[
https://issues.apache.org/jira/browse/HIVE-26121?focusedWorklogId=755133&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-755133
]
ASF GitHub Bot logged work on HIVE-26121:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Apr/22 08:34
Start Date: 11/Apr/22 08:34
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on PR #3181:
URL: https://github.com/apache/hive/pull/3181#issuecomment-1094709982
> endTransactionAndCleanup
yes, we definitely need to synchronize
`DriverTxnHandler.endTransactionAndCleanup`. As for
`DbTxnManager.java.stopHeartbeat` it was already kinda synchronized and it's
possible that concurrent execution might still occur when shutdownhook is
invoked.
Issue Time Tracking
-------------------
Worklog Id: (was: 755133)
Time Spent: 50m (was: 40m)
> Hive transaction rollback should be thread-safe
> -----------------------------------------------
>
> Key: HIVE-26121
> URL: https://issues.apache.org/jira/browse/HIVE-26121
> Project: Hive
> Issue Type: Task
> Reporter: Denys Kuzmenko
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When Hive query is being interrupted via cancel request, both the background
> pool thread (HiveServer2-Background) executing the query and the HttpHandler
> thread (HiveServer2-Handler) running the HiveSession.cancelOperation logic
> will eventually trigger the below method:
> {code}
> DriverTxnHandler.endTransactionAndCleanup(boolean commit)
> {code}
> Since this method could be invoked concurrently we need to synchronize access
> to it, so that only 1 thread would attempt to abort the transaction and stop
> the heartbeat.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
