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
[CI] ConcurrentSnapshotsIT.testEquivalentDeletesAreDeduplicated Fails on 7.x #59608
Labels
:Distributed/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed
Meta label for distributed team
>test-failure
Triaged test failures from CI
Comments
original-brownbear
added
:Distributed/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
labels
Jul 15, 2020
Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore) |
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Jul 15, 2020
Trying to queue up snapshot deletes by blocking the delete of the latest index-N doesn't work here. The first delete will block on the delete operation but only do so after having already written the updated repository data. Since that repository data will contain no snapshots, the subsequent deletes for `*` will just fall through and complete instead of queue up. => Fixed by simply waiting on all files on master so that we block before updating the repository data and get to test the queueing of equivalent operations closes elastic#59608
Another failure: https://gradle-enterprise.elastic.co/s/afdpahqegjmny |
original-brownbear
added a commit
that referenced
this issue
Jul 15, 2020
Trying to queue up snapshot deletes by blocking the delete of the latest index-N doesn't work here. The first delete will block on the delete operation but only do so after having already written the updated repository data. Since that repository data will contain no snapshots, the subsequent deletes for `*` will just fall through and complete instead of queue up. => Fixed by simply waiting on all files on master so that we block before updating the repository data and get to test the queueing of equivalent operations closes #59608
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Jul 15, 2020
…ic#59611) Trying to queue up snapshot deletes by blocking the delete of the latest index-N doesn't work here. The first delete will block on the delete operation but only do so after having already written the updated repository data. Since that repository data will contain no snapshots, the subsequent deletes for `*` will just fall through and complete instead of queue up. => Fixed by simply waiting on all files on master so that we block before updating the repository data and get to test the queueing of equivalent operations closes elastic#59608
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Jul 15, 2020
…ic#59611) Trying to queue up snapshot deletes by blocking the delete of the latest index-N doesn't work here. The first delete will block on the delete operation but only do so after having already written the updated repository data. Since that repository data will contain no snapshots, the subsequent deletes for `*` will just fall through and complete instead of queue up. => Fixed by simply waiting on all files on master so that we block before updating the repository data and get to test the queueing of equivalent operations closes elastic#59608
original-brownbear
added a commit
that referenced
this issue
Jul 16, 2020
… (#59653) Trying to queue up snapshot deletes by blocking the delete of the latest index-N doesn't work here. The first delete will block on the delete operation but only do so after having already written the updated repository data. Since that repository data will contain no snapshots, the subsequent deletes for `*` will just fall through and complete instead of queue up. => Fixed by simply waiting on all files on master so that we block before updating the repository data and get to test the queueing of equivalent operations closes #59608
original-brownbear
added a commit
that referenced
this issue
Jul 16, 2020
… (#59654) Trying to queue up snapshot deletes by blocking the delete of the latest index-N doesn't work here. The first delete will block on the delete operation but only do so after having already written the updated repository data. Since that repository data will contain no snapshots, the subsequent deletes for `*` will just fall through and complete instead of queue up. => Fixed by simply waiting on all files on master so that we block before updating the repository data and get to test the queueing of equivalent operations closes #59608
malpani
pushed a commit
to malpani/elasticsearch
that referenced
this issue
Jul 17, 2020
…ic#59611) Trying to queue up snapshot deletes by blocking the delete of the latest index-N doesn't work here. The first delete will block on the delete operation but only do so after having already written the updated repository data. Since that repository data will contain no snapshots, the subsequent deletes for `*` will just fall through and complete instead of queue up. => Fixed by simply waiting on all files on master so that we block before updating the repository data and get to test the queueing of equivalent operations closes elastic#59608
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed
Meta label for distributed team
>test-failure
Triaged test failures from CI
This only fails on 7.x and 7.9 it seems and just now started after back porting the concurrent snapshot logic.
In https://gradle-enterprise.elastic.co/s/e7obweucvwtv4/tests/:server:internalClusterTest/org.elasticsearch.snapshots.ConcurrentSnapshotsIT/testEquivalentDeletesAreDeduplicated#1
fails with:
This reproduces locally after a few iterations also. Looks like this is likely a test infra issue somehow since the relevant code seems to be the same between master and
7.x
but either way I'm on it.The text was updated successfully, but these errors were encountered: