-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Fix flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint #17216
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 flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint #17216
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #17216 +/- ##
============================================
+ Coverage 72.29% 72.39% +0.10%
- Complexity 65900 66014 +114
============================================
Files 5350 5350
Lines 306185 306208 +23
Branches 44373 44375 +2
============================================
+ Hits 221347 221688 +341
+ Misses 66670 66362 -308
+ Partials 18168 18158 -10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
...er/src/internalClusterTest/java/org/opensearch/indices/replication/SegmentReplicationIT.java
Show resolved
Hide resolved
This PR is stalled because it has been open for 30 days with no activity. |
Signed-off-by: skumwt <skumwt@amazon.com>
eed1d1b
to
b73b853
Compare
❌ Gradle check result for b73b853: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
b73b853
to
242ab74
Compare
❕ Gradle check result for 242ab74: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Signed-off-by: Sandeep Kumawat <skumwt@amazon.com> Signed-off-by: skumwt <skumwt@amazon.com>
242ab74
to
2fc5a6f
Compare
❌ Gradle check result for 2fc5a6f: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
@skumawat2025 Lets get the build to green. |
@ashking94 @skumawat2025 Looks like the failure is due to flaky tests. I have retried once |
…pensearch-project#17216) * Fix flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint Signed-off-by: skumwt <skumwt@amazon.com> * Fix flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint Signed-off-by: Sandeep Kumawat <skumwt@amazon.com> Signed-off-by: skumwt <skumwt@amazon.com> --------- Signed-off-by: skumwt <skumwt@amazon.com> Signed-off-by: Sandeep Kumawat <skumwt@amazon.com> Co-authored-by: skumwt <skumwt@amazon.com> Signed-off-by: Sriram Ganesh <srignsh22@gmail.com>
…pensearch-project#17216) * Fix flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint Signed-off-by: skumwt <skumwt@amazon.com> * Fix flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint Signed-off-by: Sandeep Kumawat <skumwt@amazon.com> Signed-off-by: skumwt <skumwt@amazon.com> --------- Signed-off-by: skumwt <skumwt@amazon.com> Signed-off-by: Sandeep Kumawat <skumwt@amazon.com> Co-authored-by: skumwt <skumwt@amazon.com> Signed-off-by: Harsh Kothari <techarsh@amazon.com>
…pensearch-project#17216) * Fix flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint Signed-off-by: skumwt <skumwt@amazon.com> * Fix flaky test SegmentReplicationIT.testReplicaAlreadyAtCheckpoint Signed-off-by: Sandeep Kumawat <skumwt@amazon.com> Signed-off-by: skumwt <skumwt@amazon.com> --------- Signed-off-by: skumwt <skumwt@amazon.com> Signed-off-by: Sandeep Kumawat <skumwt@amazon.com> Co-authored-by: skumwt <skumwt@amazon.com> Signed-off-by: Harsh Kothari <techarsh@amazon.com>
Description
In the SegmentReplicationIT.testReplicaAlreadyAtCheckpoint test, we are creating three nodes with one primary node and two replica nodes. After ingesting documents to the primary shard, we are not checking if the segment replication to both replica 1 and 2 has finished. Without verifying this, we are stopping the primary node. This behavior leads to the test being flaky when the replication has not completed.
With this change we are ensuring replication has finished before stopping the primary node.
Related Issues
Resolves #14328
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.