-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] o.o.cluster.ClusterHealthIT.testHealthOnMasterFailover test failure #1693
Comments
The test failure in gradle check log:
|
Another occurrence here: https://fork-jenkins.searchservices.aws.dev/job/OpenSearch_CI/job/PR_Checks/job/Gradle_Check/1445/ |
The assertion that fails is here: which is asserting that the response to the get health call is a success, and it fails with with a MasterNotDiscoveredException. I was able to semi-regularly reproduce this error on my Mac, and tracked it down in the debugger to be coming from the timeout here: |
Another failure on #1742 PR.
|
Another one in #1791 |
Looking into it |
After running tests multiple times, depicts that failure is more prolific when index creation is enabled and master node timeout is lesser. |
Failure occurrences are related to master node timeout and whether index creation is enabled or not. A summary of test failures based on above two properties.
|
The experiment shows that master node generally takes more time to boot up when indices are used for the test. Next Steps:
|
Created new issue to debug/improve higher bootup time for master when indices are used. |
@opensearch-project/opensearch-core team, please take a look at Build 1420 in gradle_check log for more information.
The text was updated successfully, but these errors were encountered: