Fix flaky PitMultiNodeTests including testCreatePitWhileNodeDropWithAllowPartialCreationFalse #5655
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.
Signed-off-by: Daniel Widdis [email protected]
Description
#4030 introduced a Point In Time Node Stats API and added stats validation to many PitMultiNodeTests.
Thorough debugging of flaky
testCreatePitWhileNodeDropWithAllowPartialCreationFalse()
revealed that the transLog consistently had a pending commit when the test failed (repro 1/500 runs)Flushing the index prior to collecting/validating stats resolves this failure (tested 1000 runs) and probably prevents other flaky test results.
Flushing frequently should be considered a best practice for test hygiene.
Issues Resolved
Fixes #4259 (which was previously closed associated with an unrelated fix).
Fixes comments #4089 (comment) although the issue itself was fixed by a different PR.
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.