-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove automatically deleting indices for orphaned jobs #2038
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add backport versions and the release_note label + description section?
💔 Failed to create backport PR(s)
To backport manually run: |
(cherry picked from commit 2ecbfed) # Conflicts: # connectors/services/job_cleanup.py # tests/services/test_job_cleanup.py
(cherry picked from commit 2ecbfed) # Conflicts: # connectors/services/job_cleanup.py # tests/services/test_job_cleanup.py
(cherry picked from commit 2ecbfed) # Conflicts: # connectors/services/job_cleanup.py # tests/services/test_job_cleanup.py
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
#2039) Co-authored-by: Sander Philipse <[email protected]>
#2041) Co-authored-by: Sander Philipse <[email protected]>
#2040) Co-authored-by: Sander Philipse <[email protected]>
relates to: https://github.com/elastic/enterprise-search-team/issues/6075
This removes deleting indices for orphaned jobs, as we may be inadvertently deleting indices that should be kept in some edge cases.
Release note
On some edge cases where Elasticsearch is facing issues we may be inadvertently deleting content indices, because we incorrectly think the index has been deleted. This change removes the step where we delete indices.