Skip to content

Conversation

@tlrx
Copy link
Member

@tlrx tlrx commented Oct 25, 2021

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-cache

Closes #78993

@tlrx tlrx added >test Issues or PRs that are addressing/adding tests :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs v8.0.0 v7.16.1 labels Oct 25, 2021
@elasticmachine elasticmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Oct 25, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@tlrx tlrx requested a review from arteam October 26, 2021 07:22
Copy link
Contributor

@henningandersen henningandersen left a 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-*")
Copy link
Contributor

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-*")?

@tlrx tlrx added auto-backport-and-merge auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) labels Oct 27, 2021
@elasticsearchmachine elasticsearchmachine merged commit 4003ab7 into elastic:master Oct 27, 2021
tlrx added a commit to tlrx/elasticsearch that referenced this pull request Oct 27, 2021
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
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.0 The branch "8.0" is invalid or doesn't exist
7.16

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 79747

@tlrx
Copy link
Member Author

tlrx commented Oct 27, 2021

Thanks Henning

@tlrx tlrx deleted the fix-78993 branch October 27, 2021 08:12
tlrx added a commit to tlrx/elasticsearch that referenced this pull request Oct 27, 2021
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
tlrx added a commit to tlrx/elasticsearch that referenced this pull request Oct 27, 2021
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
tlrx added a commit to tlrx/elasticsearch that referenced this pull request Oct 27, 2021
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
@tlrx
Copy link
Member Author

tlrx commented Oct 27, 2021

Annoying test failure so I backported on all affected branches.

elasticsearchmachine pushed a commit that referenced this pull request Oct 27, 2021
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-cache`  Closes #78993
elasticsearchmachine pushed a commit that referenced this pull request Oct 27, 2021
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-cache`  Closes #78993
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. >test Issues or PRs that are addressing/adding tests v7.13.5 v7.14.3 v7.15.2 v7.16.0 v8.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] SearchableSnapshotsBlobStoreCacheIntegTests testBlobStoreCache failing

6 participants