-
Notifications
You must be signed in to change notification settings - Fork 1.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
[BUG] Flaky test failure SegmentReplicationAllocationIT.testAllocationWithDisruption #6565
Comments
Able to reproduce the issue consistently with the random seed |
One more unstable gradle run: https://build.ci.opensearch.org/job/gradle-check/12707 |
The test failure here is due to the condition when only 1 node was added but 2 were stopped resulting in lesser number of nodes where re-balance is not possible due to SameShardAllocationDecider. Stopping more number of nodes is problematic when we starts with |
Even with #6838 fix, the test occassionally fails. It fails with same reason where target node can not accept primary shard due to Example failure.
|
Increasing starting node count to 5 also does not help this is due to number of existing primary shard count (5), which results in a possibility where one node (say N1) contains more number of primary shard(2), while one node (say N2) contains both the replicas and no primary and remaining 3 nodes contain one primary each (balanced). This prevents primary relocation from N1 -> N2 due to SameShardAllocationDecider. One example came up from failing test locally representing above state. Node
Finally, increased the number of nodes to [5,10] and used 2 as max shard count, after which the test doesn't fail anymore. Updated the PR. |
Describe the bug
SegmentReplicationAllocationIT is failing randomly, test name : testAllocationWithDisruption
Failure link - https://build.ci.opensearch.org/job/gradle-check/12003/testReport/junit/org.opensearch.indices.replication/SegmentReplicationAllocationIT/testAllocationWithDisruption/
To Reproduce
PR build
Expected behavior
Test should pass all the time.
Plugins
N/A
Screenshots
N/A
The text was updated successfully, but these errors were encountered: