Open
Conversation
Signed-off-by: bowenlan-amzn <bowenlan23@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1575 +/- ##
==========================================
- Coverage 76.51% 76.49% -0.03%
==========================================
Files 381 381
Lines 18069 18069
Branches 2503 2503
==========================================
- Hits 13826 13821 -5
- Misses 2975 2983 +8
+ Partials 1268 1265 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix flaky multi-node ISM tests by waiting for cluster GREEN before index cleanup
Summary
Test plan
Description
Problem
Multi-node ISM integration tests occasionally fail with cascade errors after a ClosedByInterruptException corrupts a node's file lock. Once corrupted, the affected node cannot perform any shard operations, causing all subsequent tests to fail.
Root cause timeline:
Evidence from logs:
19:27:43,350 - .opendistro-ism-config shard allocated
19:27:43,538 - Index deletion started (only 188ms later!)
19:27:43,593 - ClosedByInterruptException - node lock invalidated
19:27:43,602 - "FileLock invalidated by an external force"
Solution
Wait for cluster health to be GREEN before deleting indices in multi-node tests. When cluster is GREEN, all shards are allocated with no recoveries in progress, making index deletion safe.
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
--signoff.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.