[CI] AutoFollowIT testAutoFollowSearchableSnapshotsFails failing #74486
Assignees
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
Comments
romseygeek
added
:Distributed Indexing/CCR
elasticmachine
added
the
Team:Distributed (Obsolete)
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
Possibly related to #71556 |
tlrx
added a commit
to tlrx/elasticsearch
that referenced
this issue
Jun 28, 2021
…4498) The test AutoFollowIT.testAutoFollowSearchableSnapshotsFails was added in elastic#70580 in order to test that mounted indices of a leader cluster are not auto-followed in a follower cluster using CCR. This test sometimes fails because it expects 2 indices to be followed (the -regular and the -index indices) but not the mounted one. This looks wrong as the -index index is deleted soon after it is snapshotted, and this index only exist to create a snapshot that can be later mounted as an index in the leader cluster. This commit changes the test so that the -index index, the repository and the snapshot are created at the beginning of the test. Then the test creates the mounted index and the regular one and can now asserts that only the regular one was auto-followed. Closes elastic#74486
tlrx
added a commit
that referenced
this issue
Jun 28, 2021
The test AutoFollowIT.testAutoFollowSearchableSnapshotsFails was added in #70580 in order to test that mounted indices of a leader cluster are not auto-followed in a follower cluster using CCR. This test sometimes fails because it expects 2 indices to be followed (the -regular and the -index indices) but not the mounted one. This looks wrong as the -index index is deleted soon after it is snapshotted, and this index only exist to create a snapshot that can be later mounted as an index in the leader cluster. This commit changes the test so that the -index index, the repository and the snapshot are created at the beginning of the test. Then the test creates the mounted index and the regular one and can now asserts that only the regular one was auto-followed. Backport of #74498 Closes #74486
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/vi7pyawinxxrm/tests/:x-pack:plugin:ccr:qa:multi-cluster:follow-cluster/org.elasticsearch.xpack.ccr.AutoFollowIT/testAutoFollowSearchableSnapshotsFails
Reproduction line:
./gradlew ':x-pack:plugin:ccr:qa:multi-cluster:follow-cluster' --tests "org.elasticsearch.xpack.ccr.AutoFollowIT.testAutoFollowSearchableSnapshotsFails" -Dtests.seed=38904B6F32A23164 -Dtests.locale=sk -Dtests.timezone=Africa/Harare -Druntime.java=8Applicable branches:
master, 7.x
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.ccr.AutoFollowIT&tests.test=testAutoFollowSearchableSnapshotsFails
Failure excerpt:
The text was updated successfully, but these errors were encountered: