-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Zen2: Move disruption tests to Zen2 #35724
Conversation
Pinging @elastic/es-distributed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I left comments but only about code that's hopefully going away soon. I am still running the tests but they've passed once so I'll open followups if they find anything.
FollowersChecker.FOLLOWER_CHECK_RETRY_COUNT_SETTING, | ||
LeaderChecker.LEADER_CHECK_TIMEOUT_SETTING, | ||
LeaderChecker.LEADER_CHECK_INTERVAL_SETTING, | ||
LeaderChecker.LEADER_CHECK_RETRY_COUNT_SETTING, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops.
return nodes; | ||
} | ||
|
||
protected void clearTemporalResponses() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This thing is weird: it clears out the received pings from a single randomly-chosen node in the cluster. It was weird before this change too. But it will go away soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it's weird. I did not think it was worth investigating further there because this is going away soon.
() -> { | ||
final Discovery discovery = internalCluster().getInstance(Discovery.class, node); | ||
if (discovery instanceof ZenDiscovery) { | ||
return !((ZenDiscovery) discovery).joiningCluster(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
☠️ == false
But it will go away soon.
Thanks @DaveCTurner |
.put(TestZenDiscovery.USE_ZEN2.getKey(), true)
from tests where Zen2 is now enabled by default through the parent test classQuorumGatewayIT
back to Zen1, as it is not stable with Zen2 as it currently relies on dangling indices due to the lack of proper CS persistence, which triggers secondary failures