-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
[CI] CloseWhileRelocatingShardsIT.testCloseWhileRelocatingShards failures #38090
Comments
I don't see any failures on master, maybe the fix in #37274 didn't work for 6.x ? |
This was muted in fe0a52e |
@atorok The issue here is a bit different so I told Alan to create a new issue. |
The current CloseWhileRelocatingShardsIT test adds some "send behavior" rule to a target node's mocked transport service in order to detect when shard relocating are started. These rules are never cleared and prevent the test to complete normally after the rebalance is re-enabled again. This commit changes the test so that rules are cleared and most verifications are done before the rebalance is reenabled again. Closes #38090
The current CloseWhileRelocatingShardsIT test adds some "send behavior" rule to a target node's mocked transport service in order to detect when shard relocating are started. These rules are never cleared and prevent the test to complete normally after the rebalance is re-enabled again. This commit changes the test so that rules are cleared and most verifications are done before the rebalance is reenabled again. Closes #38090
Pinging @elastic/es-distributed |
I just saw another failure pop up on master intake: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob+fast+part1/3897/ @tlrx I'm having trouble telling whether I should re-open this issue or file a new one, figured I'd just link to the failure so you're aware. |
See https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+internalClusterTest/173/console for an example failure
It looks to be a timing issue, it doesn't reproduce for me:
The text was updated successfully, but these errors were encountered: