-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix testBlobStoreCache #79747
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
Fix testBlobStoreCache #79747
Conversation
|
Pinging @elastic/es-distributed (Team:Distributed) |
henningandersen
left a comment
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.
LGTM.
| client().admin() | ||
| .cluster() | ||
| .prepareHealth() | ||
| .setIndices("restored-*") |
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 we simplify this to ensureGreen("restored-*")?
The attempt to fix this test in elastic#78616 wasn't complete: we need to wait for all mounted indices, not only the last restored one, before deleting the indices. Otherwise one of the mounted index might still be initializing and recreates the cached documents in `.snapshot-blob-cache` Closes elastic#78993
💔 Backport failed
You can use sqren/backport to manually backport by running |
|
Thanks Henning |
The attempt to fix this test in elastic#78616 wasn't complete: we need to wait for all mounted indices, not only the last restored one, before deleting the indices. Otherwise one of the mounted index might still be initializing and recreates the cached documents in `.snapshot-blob-cache` Closes elastic#78993
The attempt to fix this test in elastic#78616 wasn't complete: we need to wait for all mounted indices, not only the last restored one, before deleting the indices. Otherwise one of the mounted index might still be initializing and recreates the cached documents in `.snapshot-blob-cache` Closes elastic#78993
The attempt to fix this test in elastic#78616 wasn't complete: we need to wait for all mounted indices, not only the last restored one, before deleting the indices. Otherwise one of the mounted index might still be initializing and recreates the cached documents in `.snapshot-blob-cache` Closes elastic#78993
|
Annoying test failure so I backported on all affected branches. |
The attempt to fix this test in #78616 wasn't complete: we need to wait for all mounted indices, not only the last restored one, before deleting the indices. Otherwise one of the mounted index might still be initializing and recreates the cached documents in
.snapshot-blob-cacheCloses #78993