-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Change IOContext from READONCE to DEFAULT to avoid WrongThreadException #17502
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
Conversation
Signed-off-by: Sachin Kale <[email protected]>
Created an issue to run remote store integ tests with different repository plugin implementations: #17503 |
❌ Gradle check result for 23319dd: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Test failing with:
Taking a look |
❌ Gradle check result for 23319dd: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Fixed the test failures as part of latest commit |
❕ Gradle check result for 553ef13: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add an assertion on here on the IOContext to ensure all uploads have IOContext
correctly set
Signed-off-by: Sachin Kale <[email protected]>
❌ Gradle check result for e762397: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Sachin Kale <[email protected]>
❌ Gradle check result for c8904cd: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for c8904cd: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❕ Gradle check result for c8904cd: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #17502 +/- ##
============================================
+ Coverage 72.47% 72.57% +0.09%
- Complexity 65705 65741 +36
============================================
Files 5307 5307
Lines 304774 304775 +1
Branches 44193 44193
============================================
+ Hits 220898 221197 +299
+ Misses 65738 65463 -275
+ Partials 18138 18115 -23 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-17502-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 588f46d731587bebd54511dc2df21a2f4ffb9f32
# Push it to GitHub
git push --set-upstream origin backport/backport-17502-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.19 2.19
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.19
# Create a new branch
git switch --create backport/backport-17502-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 588f46d731587bebd54511dc2df21a2f4ffb9f32
# Push it to GitHub
git push --set-upstream origin backport/backport-17502-to-2.19
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.19 Then, create a pull request where the |
…on (opensearch-project#17502) --------- Signed-off-by: Sachin Kale <[email protected]>
…on (opensearch-project#17502) --------- Signed-off-by: Sachin Kale <[email protected]>
…on (#17502) (#17545) --------- Signed-off-by: Sachin Kale <[email protected]>
…on (#17502) (#17544) --------- Signed-off-by: Sachin Kale <[email protected]>
…on (opensearch-project#17502) --------- Signed-off-by: Sachin Kale <[email protected]> Signed-off-by: Vinay Krishna Pudyodu <[email protected]>
Description
DEFAULT
toREADONCE
.java.lang.WrongThreadException: Attempted access outside owning thread
.repository-s3
where IndexInput is getting close in the following code flow.OpenSearch/server/src/main/java/org/opensearch/common/blobstore/transfer/stream/OffsetRangeIndexInputStream.java
Lines 149 to 162 in f6d6aa6
Related Issues
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.