[CI] ReplicaShardAllocatorIT testPreferCopyWithHighestMatchingOperations failing #74081
Assignees
Labels
:Distributed/Allocation
All issues relating to the decision making around placing a shard (both master logic & on the nodes)
Team:Distributed
Meta label for distributed team
>test-failure
Triaged test failures from CI
Comments
benwtrent
added
:Distributed/Allocation
|
Pinging @elastic/es-distributed (Team:Distributed) |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Jul 9, 2021
In elastic#74081 this test failed with a `NoNodeAvailableException` within the `indexRandom()` call immediately after stopping a node. This could happen if the `node-left` event wasn't fully applied before calling `indexRandom()` with an empty list of docs but with `forceRefresh` set to true: since there's no docs, the replica wouldn't be marked as stale, so the final refresh would detect the missing node, failing its `assertNoFailures` wrapper. This commit avoids calling `indexRandom()` with no docs in this location. It also enhances `assertNoFailures` to report the details of each failure, rather than just the summary. Closes elastic#74081
DaveCTurner
added a commit
that referenced
this issue
Jul 13, 2021
In #74081 this test failed with a `NoNodeAvailableException` within the `indexRandom()` call immediately after stopping a node. This could happen if the `node-left` event wasn't fully applied before calling `indexRandom()` with an empty list of docs but with `forceRefresh` set to true: since there's no docs, the replica wouldn't be marked as stale, so the final refresh would detect the missing node, failing its `assertNoFailures` wrapper. This commit avoids calling `indexRandom()` with no docs in this location. It also enhances `assertNoFailures` to report the details of each failure, rather than just the summary. Closes #74081
DaveCTurner
added a commit
that referenced
this issue
Jul 13, 2021
In #74081 this test failed with a `NoNodeAvailableException` within the `indexRandom()` call immediately after stopping a node. This could happen if the `node-left` event wasn't fully applied before calling `indexRandom()` with an empty list of docs but with `forceRefresh` set to true: since there's no docs, the replica wouldn't be marked as stale, so the final refresh would detect the missing node, failing its `assertNoFailures` wrapper. This commit avoids calling `indexRandom()` with no docs in this location. It also enhances `assertNoFailures` to report the details of each failure, rather than just the summary. Closes #74081
DaveCTurner
added a commit
that referenced
this issue
Jul 13, 2021
In #74081 this test failed with a `NoNodeAvailableException` within the `indexRandom()` call immediately after stopping a node. This could happen if the `node-left` event wasn't fully applied before calling `indexRandom()` with an empty list of docs but with `forceRefresh` set to true: since there's no docs, the replica wouldn't be marked as stale, so the final refresh would detect the missing node, failing its `assertNoFailures` wrapper. This commit avoids calling `indexRandom()` with no docs in this location. It also enhances `assertNoFailures` to report the details of each failure, rather than just the summary. Closes #74081
DaveCTurner
added a commit
that referenced
this issue
Jul 13, 2021
In #74081 this test failed with a `NoNodeAvailableException` within the `indexRandom()` call immediately after stopping a node. This could happen if the `node-left` event wasn't fully applied before calling `indexRandom()` with an empty list of docs but with `forceRefresh` set to true: since there's no docs, the replica wouldn't be marked as stale, so the final refresh would detect the missing node, failing its `assertNoFailures` wrapper. This commit avoids calling `indexRandom()` with no docs in this location. It also enhances `assertNoFailures` to report the details of each failure, rather than just the summary. Closes #74081
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build scan:
https://gradle-enterprise.elastic.co/s/5x3nuaw4ehzzm/tests/:server:internalClusterTest/org.elasticsearch.gateway.ReplicaShardAllocatorIT/testPreferCopyWithHighestMatchingOperations
Reproduction line:
./gradlew ':server:internalClusterTest' --tests "org.elasticsearch.gateway.ReplicaShardAllocatorIT.testPreferCopyWithHighestMatchingOperations" -Dtests.seed=E84FA673AF3C8429 -Dtests.locale=sk -Dtests.timezone=Brazil/East -Druntime.java=8Applicable branches:
7.13
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.gateway.ReplicaShardAllocatorIT&tests.test=testPreferCopyWithHighestMatchingOperations
Failure excerpt:
The text was updated successfully, but these errors were encountered: