-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] RebalanceAfterActiveTests testRebalanceOnlyAfterAllShardsAreActive failing #94086
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
Comments
Pinging @elastic/es-distributed (Team:Distributed) |
The test is failing around this line: Line 137 in 9cb71ee
In short test is doing following:
A new desired balance is calculated in a way that one of the indices expected nodes are ones where it already allocated (so one of the replicas do not need to move):
|
Your analysis looks right to me, yes. One question:
Do you know where that rule is implemented? |
This was added with initial file commit in 2010 for 0.9 version. |
Build scan:
https://gradle-enterprise.elastic.co/s/xdilv3b7y5lzq/tests/:server:test/org.elasticsearch.cluster.routing.allocation.RebalanceAfterActiveTests/testRebalanceOnlyAfterAllShardsAreActive
Reproduction line:
Applicable branches:
main
Reproduces locally?:
Yes
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.cluster.routing.allocation.RebalanceAfterActiveTests&tests.test=testRebalanceOnlyAfterAllShardsAreActive
Failure excerpt:
The text was updated successfully, but these errors were encountered: