-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] org.opensearch.search.sort.FieldSortIT.testIssue6614 is flaky #11347
Comments
Looking through the test failures, the failures are not taking place at the same spot. Looking into the main failure of |
From printing the |
Below are some of the important configurable params for this test: 250*3 = 750 = This will be the max number of shards for this test which could result in "too many open files". Reran test with all |
@Poojita-Raj Looks like we've seen this resurface - it is possible that this failure happened because the filesystem/constraints on the Jenkins worker are different than where you validated the max configuration? Naive question; is there value in the number of max indices being 25 vs 5 seems like a quick fix?
|
Closing in favour of #14287 |
Describe the bug
The test case org.opensearch.search.sort.FieldSortIT.testIssue6614 is flaky:
To Reproduce
Expected behavior
The test should always pass
Plugins
Standard
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: