-
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
CardinalityIT/NestedIT test failures with concurrent search enabled and AssertingCodec #8303
Conversation
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## main #8303 +/- ##
============================================
+ Coverage 70.93% 71.00% +0.06%
+ Complexity 57184 57108 -76
============================================
Files 4770 4760 -10
Lines 270280 269725 -555
Branches 39499 39460 -39
============================================
- Hits 191726 191520 -206
+ Misses 62439 62069 -370
- Partials 16115 16136 +21
|
@reta Can you please help to review ? |
server/src/main/java/org/opensearch/search/internal/ContextIndexSearcher.java
Outdated
Show resolved
Hide resolved
Gradle Check (Jenkins) Run Completed with:
|
Failed tests are unrelated:
|
server/src/main/java/org/opensearch/search/aggregations/BucketCollectorProcessor.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/search/internal/ContextIndexSearcher.java
Show resolved
Hide resolved
server/src/main/java/org/opensearch/search/aggregations/BucketCollectorProcessor.java
Show resolved
Hide resolved
@sohami could you please add changelog (may be using different phrasing), it seems we are changing not the tests but core functionality. |
Gradle Check (Jenkins) Run Completed with:
|
Added the changelog entry |
Gradle Check (Jenkins) Run Completed with:
|
@reta Can this be merged ? |
…nd AssertingCodec The tests were failing because during the concurrent segment search for each slice the codec producers for the leafs were initialized by the slice thread. Later in reduce phase, the post collection happens over those codec producers on the search thread. With AssertingCodec it verifies that all access is done by the same thread causing the failures Signed-off-by: Sorabh Hamirwasia <[email protected]>
Signed-off-by: Sorabh Hamirwasia <[email protected]>
I did rebase yesterday as part of final commit and gradle seems to be failing for bwc2.9 jar. Let me rebase again to see if that fixes below issue.
|
Gradle Check (Jenkins) Run Completed with:
|
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8303-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 064f265362f6ae8296bfeed09aaaf48be86e6a4d
# Push it to GitHub
git push --set-upstream origin backport/backport-8303-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x Then, create a pull request where the |
Hehe @sohami please backport manually to |
…nd AssertingCodec (opensearch-project#8303) * CardinalityIT/NestedIT test failures with concurrent search enabled and AssertingCodec The tests were failing because during the concurrent segment search for each slice the codec producers for the leafs were initialized by the slice thread. Later in reduce phase, the post collection happens over those codec producers on the search thread. With AssertingCodec it verifies that all access is done by the same thread causing the failures Signed-off-by: Sorabh Hamirwasia <[email protected]> * Address review comments Signed-off-by: Sorabh Hamirwasia <[email protected]> --------- Signed-off-by: Sorabh Hamirwasia <[email protected]>
…nd AssertingCodec (#8303) (#8687) * CardinalityIT/NestedIT test failures with concurrent search enabled and AssertingCodec The tests were failing because during the concurrent segment search for each slice the codec producers for the leafs were initialized by the slice thread. Later in reduce phase, the post collection happens over those codec producers on the search thread. With AssertingCodec it verifies that all access is done by the same thread causing the failures * Address review comments --------- Signed-off-by: Sorabh Hamirwasia <[email protected]>
…nd AssertingCodec (opensearch-project#8303) * CardinalityIT/NestedIT test failures with concurrent search enabled and AssertingCodec The tests were failing because during the concurrent segment search for each slice the codec producers for the leafs were initialized by the slice thread. Later in reduce phase, the post collection happens over those codec producers on the search thread. With AssertingCodec it verifies that all access is done by the same thread causing the failures Signed-off-by: Sorabh Hamirwasia <[email protected]> * Address review comments Signed-off-by: Sorabh Hamirwasia <[email protected]> --------- Signed-off-by: Sorabh Hamirwasia <[email protected]> Signed-off-by: sahil buddharaju <[email protected]>
…nd AssertingCodec (opensearch-project#8303) * CardinalityIT/NestedIT test failures with concurrent search enabled and AssertingCodec The tests were failing because during the concurrent segment search for each slice the codec producers for the leafs were initialized by the slice thread. Later in reduce phase, the post collection happens over those codec producers on the search thread. With AssertingCodec it verifies that all access is done by the same thread causing the failures Signed-off-by: Sorabh Hamirwasia <[email protected]> * Address review comments Signed-off-by: Sorabh Hamirwasia <[email protected]> --------- Signed-off-by: Sorabh Hamirwasia <[email protected]>
…nd AssertingCodec (opensearch-project#8303) * CardinalityIT/NestedIT test failures with concurrent search enabled and AssertingCodec The tests were failing because during the concurrent segment search for each slice the codec producers for the leafs were initialized by the slice thread. Later in reduce phase, the post collection happens over those codec producers on the search thread. With AssertingCodec it verifies that all access is done by the same thread causing the failures Signed-off-by: Sorabh Hamirwasia <[email protected]> * Address review comments Signed-off-by: Sorabh Hamirwasia <[email protected]> --------- Signed-off-by: Sorabh Hamirwasia <[email protected]> Signed-off-by: Shivansh Arora <[email protected]>
Description
The tests were failing because during the concurrent segment search for each slice the codec producers for the leafs were initialized by the slice thread. Later in reduce phase, the post collection happens over those codec producers on the search thread. With AssertingCodec it verifies that all access is done by the same thread causing the failures. More details are in #8095
Related Issues
Resolves #8095
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.