-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] Failure in SearchableSnapshotsIntegTests.testCreateAndRestoreSearchableSnapshot #63586
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed
Meta label for distributed team (obsolete)
>test-failure
Triaged test failures from CI
Comments
original-brownbear
added
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
labels
Oct 13, 2020
Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore) |
elasticmachine
added
the
Team:Distributed
Meta label for distributed team (obsolete)
label
Oct 13, 2020
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Oct 20, 2020
Replacing the mechanism for eviction and listener references via a read-write lock by a reference counting implementation. This fixes a bug that caused test failure elastic#63586 in which concurrently trying to acquire or release an eviction listener while doing a file operation would sometimes lead to throwing an exception since the `tryLock` call on the read lock would fail in this case. Also this removes the possibility of blocking cluster state updates as a result of them waiting on the write-lock which might take a long time if a slow read operation executes concurrently. Closes elastic#63586
original-brownbear
added a commit
that referenced
this issue
Oct 23, 2020
Replacing the mechanism for eviction and listener references via a read-write lock by a reference counting implementation. This fixes a bug that caused test failure #63586 in which concurrently trying to acquire or release an eviction listener while doing a file operation would sometimes lead to throwing an exception since the `tryLock` call on the read lock would fail in this case. Also this removes the possibility of blocking cluster state updates as a result of them waiting on the write-lock which might take a long time if a slow read operation executes concurrently. Closes #63586
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Oct 26, 2020
Replacing the mechanism for eviction and listener references via a read-write lock by a reference counting implementation. This fixes a bug that caused test failure elastic#63586 in which concurrently trying to acquire or release an eviction listener while doing a file operation would sometimes lead to throwing an exception since the `tryLock` call on the read lock would fail in this case. Also this removes the possibility of blocking cluster state updates as a result of them waiting on the write-lock which might take a long time if a slow read operation executes concurrently. Closes elastic#63586
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Oct 26, 2020
Replacing the mechanism for eviction and listener references via a read-write lock by a reference counting implementation. This fixes a bug that caused test failure elastic#63586 in which concurrently trying to acquire or release an eviction listener while doing a file operation would sometimes lead to throwing an exception since the `tryLock` call on the read lock would fail in this case. Also this removes the possibility of blocking cluster state updates as a result of them waiting on the write-lock which might take a long time if a slow read operation executes concurrently. Closes elastic#63586
original-brownbear
added a commit
that referenced
this issue
Oct 26, 2020
Replacing the mechanism for eviction and listener references via a read-write lock by a reference counting implementation. This fixes a bug that caused test failure #63586 in which concurrently trying to acquire or release an eviction listener while doing a file operation would sometimes lead to throwing an exception since the `tryLock` call on the read lock would fail in this case. Also this removes the possibility of blocking cluster state updates as a result of them waiting on the write-lock which might take a long time if a slow read operation executes concurrently. Closes #63586
original-brownbear
added a commit
that referenced
this issue
Oct 26, 2020
Replacing the mechanism for eviction and listener references via a read-write lock by a reference counting implementation. This fixes a bug that caused test failure #63586 in which concurrently trying to acquire or release an eviction listener while doing a file operation would sometimes lead to throwing an exception since the `tryLock` call on the read lock would fail in this case. Also this removes the possibility of blocking cluster state updates as a result of them waiting on the write-lock which might take a long time if a slow read operation executes concurrently. Closes #63586
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed
Meta label for distributed team (obsolete)
>test-failure
Triaged test failures from CI
This failed both on 7.x and
master
.Given enough iterations (I'm able to reproduce this locally):
relatively reliably fails with:
as it did in https://gradle-enterprise.elastic.co/s/4vrinfmyhhgyo
The text was updated successfully, but these errors were encountered: