-
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
[Concurrent Segment Search] IT tests failures with concurrent search enabled #7357
Comments
Created #8509 to track SigTerms related failures. I was not able to reproduce test failures for these shard size related failures:
|
|
Wasn't able to reproduce locally with the test seed Tracking this flakey test in a separate issue: #9401 |
Closing this issues as the fixes related to these are merge in and other separate issues are created for pending/new flaky tests. |
As part of this task we will run all the search IT tests with concurrent search enabled and try enforcing multiple slices to capture different test failures. Based on the findings we will make the changes to fix those. Some of the known ones are:
Fixed:
Cardinality/Nested (Tracked In #8095)
Cancellation related failures
SignificantTerms (Tracked in #8509)
- org.opensearch.search.ConcurrentSegmentSearchTimeoutIT.testSimpleTimeout
org.opensearch.search.SearchTimeoutIT.testSimpleTimeout
Profiler IT (#8801)
Shard Size parameter related failures (Tracked in #8860)
DocCountError: (#9209)
CB failures (#9124 )
Sort (Tracked in #8510)
parent-join (#9469)
:modules:parent-join:internalClusterTest
- org.opensearch.action.admin.cluster.node.tasks.ConcurrentSearchTasksIT.testConcurrentSearchTaskTracking
The text was updated successfully, but these errors were encountered: