HIVE-29735: TxnStoreMutex.releaseLocks does not release the connection on failure#6604
Open
deniskuzZ wants to merge 1 commit into
Open
HIVE-29735: TxnStoreMutex.releaseLocks does not release the connection on failure#6604deniskuzZ wants to merge 1 commit into
deniskuzZ wants to merge 1 commit into
Conversation
|
Contributor
|
@deniskuzZ , will it cause this stacktrace :-) |
Contributor
|
@deniskuzZ , can you please share the repo case/stacktrace of error you faced? I faced the above stacktrace today in prod as per timestamp. HIVE-28669 is backported in 4.0.1 in my case. So I was thinking of this in |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.



What changes were proposed in this pull request?
Complete the transaction on all paths in releaseLocks by calling
TransactionContext.close()in a finally blockWhy are the changes needed?
BugFix
Does this PR introduce any user-facing change?
No
How was this patch tested?
Local repro