-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[esArchiver] retry delete/create for non-kibana indexes which conflict with aliases #83746
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
💔 Build Failed
Failed CI Steps
Test FailuresChrome X-Pack UI Functional Tests.x-pack/test/functional/apps/security/rbac_phase1·js.security app rbac "before all" hook for "rbac all role can save a visualization"Standard Out
Stack Trace
Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/uptime.Uptime app with generated data "before each" hook: load heartbeat data for "displays the overall availability"Standard Out
Stack Trace
X-Pack Accessibility Tests.x-pack/test/accessibility/apps/roles·ts.Kibana roles page a11y tests "before all" hook for "a11y test for Roles main page"Standard Out
Stack Trace
and 11 more failures, only showing the first 3. Metrics [docs]
To update your PR or re-run it, just comment with: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #71910 I encoded an assumption that alias conflicts would always be caused by .kibana indexes, but there are other indexes which might be automatically created and pointing at an alias, like the
.kibana_task_manager
indexes. In the rare case that one of those indices is recreated in conflict with the index load being attempted by theEsArchiver
we log a warning and then retry the create function, assuming that the create function will clear the index like we do for.kibana_\d+
indexes. Instead, the clearing logic is skipped because.kibana_task_manager
doesn't match the pattern and we just keep retrying the create without improving our chances of success.This updates the logic to use the
isKibanaIndex
test from thekibana_index.ts
module everywhere, so that we're no longer treating documents for.kibana_task_manager
differently in different places of the code, and also ensures that we delete the.kibana_*
indexes which aren't saved object indexes on conflicts.