-
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
[Segment Replication] Fix testAllocationWithDisruption flakyness #6838
[Segment Replication] Fix testAllocationWithDisruption flakyness #6838
Conversation
Signed-off-by: Suraj Singh <[email protected]>
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #6838 +/- ##
============================================
+ Coverage 70.65% 70.73% +0.07%
- Complexity 59162 59220 +58
============================================
Files 4812 4812
Lines 283615 283615
Branches 40896 40896
============================================
+ Hits 200394 200615 +221
+ Misses 66764 66565 -199
+ Partials 16457 16435 -22 see 488 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
…es of primary accumulation on one node Signed-off-by: Suraj Singh <[email protected]>
Gradle Check (Jenkins) Run Completed with:
|
...ernalClusterTest/java/org/opensearch/indices/replication/SegmentReplicationAllocationIT.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Suraj Singh <[email protected]>
Gradle Check (Jenkins) Run Completed with:
|
* [Segment Replication] Fix testAllocationWithDisruption flakyness Signed-off-by: Suraj Singh <[email protected]> * Use more number of nodes with lesser primary shards to decrease chances of primary accumulation on one node Signed-off-by: Suraj Singh <[email protected]> * Update comment Signed-off-by: Suraj Singh <[email protected]> --------- Signed-off-by: Suraj Singh <[email protected]> (cherry picked from commit 7500270) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…) (#6847) * [Segment Replication] Fix testAllocationWithDisruption flakyness * Use more number of nodes with lesser primary shards to decrease chances of primary accumulation on one node * Update comment --------- (cherry picked from commit 7500270) Signed-off-by: Suraj Singh <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…nsearch-project#6838) * [Segment Replication] Fix testAllocationWithDisruption flakyness Signed-off-by: Suraj Singh <[email protected]> * Use more number of nodes with lesser primary shards to decrease chances of primary accumulation on one node Signed-off-by: Suraj Singh <[email protected]> * Update comment Signed-off-by: Suraj Singh <[email protected]> --------- Signed-off-by: Suraj Singh <[email protected]> Signed-off-by: Valentin Mitrofanov <[email protected]>
Description
The existing flakyness was due to condition when smaller number of nodes were added but more number of nodes were stopped resulting in lesser number of nodes where re-balance is not possible due to SameShardAllocationDecider. This test changes:
Issues Resolved
Resolves #6565
Testing
Ran the test in continuation with this fix, the test is not failing anymore (ran 800 times without failure).
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.