-
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.query.SearchQueryIT.testCommonTermsQuery is flaky for concurrent search as well as non-concurrent search case. #11208
Comments
Pretty sure I've tracked this down to commit bc74731. I can't reproduce the error on the commit before that, but after bc74731 I can reproduce within 10 or 20 attempts. It is still reproducible after the latest commit on main. It seems to fail for both concurrent and non-concurrent cases. @neetikasinghal can you take a look? |
Was able to confirm on the test seed above OpenSearch/test/framework/src/main/java/org/opensearch/test/OpenSearchIntegTestCase.java Lines 1685 to 1687 in 5b505ec
However with those changes the test is flaky. This is true for both concurrent search enabled and disabled cases. |
Query:
Flaky Result:
Correct Result:
|
Match All query in the flaky scenario does show the expected 3 docs in the index and no bogus docs but it seems like somehow the score for doc Additionally, I did notice that this test is using a 1/1 shard configuration. After setting the index to 0 primaries I ran the test on the same seed Current hypothesis is that the replica shard is not being refreshed even when the primary shard is so search requests routed to the replica will encounter this issue. However, the |
From testCommonTermsQuery_1.txt Both are flaky test examples, in the first we see the search request hit the replica and in the second we see the search request hit the primary. Quick excerpt:
|
It seems like there's an underlying problem with this query type itself instead of anything related to the new bogus docs indexing. |
Describe the bug
These test cases are flaky -
To Reproduce
Expected behavior
The test must always pass for both the cases.
Additional context
https://build.ci.opensearch.org/job/gradle-check/29721/
The text was updated successfully, but these errors were encountered: