-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Fix AutoFollowIT.testPauseAndResumeWithMultipleAutoFollowPatterns #48128
Conversation
Pinging @elastic/es-distributed (:Distributed/CCR) |
@elasticmachine test this please |
1 similar comment
@elasticmachine test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a smaller comment but LGTM. Thanks Tanguy.
while (running.get()) { | ||
while (running.get() && leaderIndices.get() < 20) { | ||
final String prefix = randomFrom(prefixes); | ||
final String leaderIndex = prefix + randomAlphaOfLength(10).toLowerCase(Locale.ROOT); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can have duplicate indices here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, thanks! I adapted the logic a bit to not create duplicate indices here.
@elasticmachine update branch (Lucene versions tests failed) |
Thanks @dnhatn ! |
…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
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 PR 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