-
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
[BUG] org.opensearch.search.sort.FieldSortIT.testSimpleSorts {p0={"search.concurrent_segment_search.enabled":"true"}} if flaky #11875
Comments
Able to reproduce this 100% with the provided test seed:
Exception is coming from here: OpenSearch/server/src/main/java/org/opensearch/index/fielddata/AbstractNumericDocValues.java Lines 55 to 58 in 7b75fb4
This comes from the |
This is (one of) the problematic queries: OpenSearch/server/src/internalClusterTest/java/org/opensearch/search/sort/FieldSortIT.java Line 815 in b18ee7d
|
This is interesting, I think we handle HALF_FLOAT / UNSIGNED_LONG differently but I am wondering how come the test fails from time to time? |
It looks like we encounter the problem with sort for, The problem seems to be related to this change: apache/lucene#12405 As the comparator is getting set to The if statement seems to be related to the number of documents on the segment though so it seems like we could still see this in the non-concurrent search case. |
It seems to me the naive solution here is to change this: Line 50 in 4a42150
to use @reta @mch2 as you are more familiar with the Lucene 9.9 upgrade would you mind giving a second set of eyes here? |
Describe the bug
The test case
org.opensearch.search.sort.FieldSortIT.testSimpleSorts {p0={"search.concurrent_segment_search.enabled":"true"}}
is flaky:Related component
Search
To Reproduce
Expected behavior
The test must always pass
Additional Details
Plugins
Standard
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: