-
Notifications
You must be signed in to change notification settings - Fork 25.2k
ClusterDisruptionIT#testAckedIndexing failures #41068
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
Comments
Pinging @elastic/es-distributed |
The issue here is that disruptions are not always fully healed when the test ends, which leads to failures in clean-up actions. @DaveCTurner thoughts on how to ensure this? |
Another failure encountered here: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+periodic/486/console Reproduce with:
Couldn't reproduce locally. The message is different though:
Here are the complete logs in case they're lost from ci: https://gist.github.com/matriv/ee422e416aac35910194a7319a595ed6 |
Thanks @ywelsch. |
AbstractDisruptionTestCase set a lower global checkpoint sync interval setting, but this was ignored by testAckedIndexing, which has led to spurious test failures Relates elastic#41068, elastic#38931
Backported this to 7.2 too, since these test-failures still show up here and this was clearly intended to go there too. |
Closing this as this issue mixed various unrelated test failures. With the most recent one being fixed, and the prior one not having shown up recently, I prefer to close this issue and instead have a new issue created once we get a newer failure. |
On master: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+artifactory/329/console
Could not reproduce locally:
The text was updated successfully, but these errors were encountered: