-
Notifications
You must be signed in to change notification settings - Fork 130
fix: gracefully handle thread interruption in ConnectionImpl to preve… #4047
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
Open
SivamuruganP
wants to merge
2
commits into
googleapis:main
Choose a base branch
from
SivamuruganP:fix/issue-3992-graceful-connection-close
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Thanks! I think the changes make sense, I just have a few questions:
java-bigquery/google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/ConnectionImpl.java
Lines 1163 to 1164 in d214d10
Thread.currentThread().interrupt()when we catch the InterruptedException thereIIUC the PR and the above correctly, then I don't think we need to explicitly catch for InterruptedException here as all interruption states should be set properly and handled cooperatively. Let me know your thoughts and if I see this incorrectly.
Uh oh!
There was an error while loading. Please reload this page.
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.
Thanks for the review! Here is the reasoning behind these checks:
Since this logic relies on gRPC (via the Arrow reader), canceling the context or closing the connection often manifests as a
CancelledExceptionrather thanInterruptedException. If we don't catch it explicitly, it falls through to theelseblock and gets logged as an error.when
connection.close()is called, the thread is usually blocked insidereader.processRows(). This blocking call immediately throws an exception upon interruption, effectively breaking out of the loop before execution can return to L1064.Below is exception stack trace I get when running
testConnectionTestlocally. You can see it hitstranslateAndThrowinstead of exiting the loop gracefully: