-
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
AutoFollowIT failures #47917
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test-failure
Triaged test failures from CI
Comments
jkakavas
added
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test-failure
Triaged test failures from CI
labels
Oct 11, 2019
Pinging @elastic/es-distributed (:Distributed/CCR) |
Merged
jkakavas
added a commit
that referenced
this issue
Oct 11, 2019
howardhuanghua
pushed a commit
to TencentCloudES/elasticsearch
that referenced
this issue
Oct 14, 2019
tlrx
added a commit
that referenced
this issue
Oct 21, 2019
…8128) The test testPauseAndResumeWithMultipleAutoFollowPatterns failed multiple times, mostly because it creates too many leader indices and the following cluster cannot cope with cluster state updates generated by following indices creation and pause/ resume auto-followers changes. This commit simplifies the test by creating at most 20 leader indices and by waiting for any new leader index to be picked up by the auto-follower before created another leader index. It also pause and resume less auto-followers as previously. closes #47917
tlrx
added a commit
to tlrx/elasticsearch
that referenced
this issue
Oct 21, 2019
…astic#48128) The test testPauseAndResumeWithMultipleAutoFollowPatterns failed multiple times, mostly because it creates too many leader indices and the following cluster cannot cope with cluster state updates generated by following indices creation and pause/ resume auto-followers changes. This commit simplifies the test by creating at most 20 leader indices and by waiting for any new leader index to be picked up by the auto-follower before created another leader index. It also pause and resume less auto-followers as previously. closes elastic#47917
This was referenced Oct 21, 2019
tlrx
added a commit
that referenced
this issue
Oct 21, 2019
…8288) The test testPauseAndResumeWithMultipleAutoFollowPatterns failed multiple times, mostly because it creates too many leader indices and the following cluster cannot cope with cluster state updates generated by following indices creation and pause/ resume auto-followers changes. This commit simplifies the test by creating at most 20 leader indices and by waiting for any new leader index to be picked up by the auto-follower before created another leader index. It also pause and resume less auto-followers as previously. closes #47917
tlrx
added a commit
that referenced
this issue
Oct 21, 2019
…8289) The test testPauseAndResumeWithMultipleAutoFollowPatterns failed multiple times, mostly because it creates too many leader indices and the following cluster cannot cope with cluster state updates generated by following indices creation and pause/ resume auto-followers changes. This commit simplifies the test by creating at most 20 leader indices and by waiting for any new leader index to be picked up by the auto-follower before created another leader index. It also pause and resume less auto-followers as previously. closes #47917
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test-failure
Triaged test failures from CI
5 tests within AutoFollowIT have been failed today:
https://gradle-enterprise.elastic.co/s/tgnjxczdo7ave/tests/htwk6wzdfugzg-7uzlsljkhp3ee
https://gradle-enterprise.elastic.co/s/tgnjxczdo7ave/tests/htwk6wzdfugzg-lunr4t27llkji
https://gradle-enterprise.elastic.co/s/jzn6aslxsi4v6/tests/htwk6wzdfugzg-c24zvdrkqeiy2
https://gradle-enterprise.elastic.co/s/jzn6aslxsi4v6/tests/htwk6wzdfugzg-7uzlsljkhp3ee
https://gradle-enterprise.elastic.co/s/hvimqd7ekwr7e/tests/htwk6wzdfugzg-7uzlsljkhp3ee
The text was updated successfully, but these errors were encountered: