-
Notifications
You must be signed in to change notification settings - Fork 25.2k
StableMasterDisruptionIT.testStaleMasterNotHijackingMajority failing in CI #43392
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 test is using Relevant log lines:
|
Relates #43387 |
@ywelsch yea it certainly looks like suspending the node threads is to blame here most likely. It seems to me like that's the only action we take that could affect multiple selectors at once. I'll look into this shortly, if I remember correctly there were some issues with suspending threads and socket channels in JDK8. |
* Let's log the state of the thread to find out if it's dead-locked or just stuck after being suspended * Relates elastic#43392
I think the added logging of the stuck thread's state in #43424 should suffice to figure out if this is a result of the thread suspend call. |
* Let's log the state of the thread to find out if it's dead-locked or just stuck after being suspended * Relates #43392
* Let's log the state of the thread to find out if it's dead-locked or just stuck after being suspended * Relates elastic#43392
* Let's log the state of the thread to find out if it's dead-locked or just stuck after being suspended * Relates elastic#43392
Failure tracked in #43387 |
In the last 6 days (since about June 13), there's been an uptick in failures pertaining to this test case.
The offending assertion looks like its:
Failing with:
Gradle Scan from 13th: https://scans.gradle.com/s/tfwcqwg266oam
Scan from today: https://scans.gradle.com/s/2edje7yces7zc
The text was updated successfully, but these errors were encountered: