[
https://issues.apache.org/jira/browse/HIVE-27201?focusedWorklogId=858390&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858390
]
ASF GitHub Bot logged work on HIVE-27201:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Apr/23 08:47
Start Date: 21/Apr/23 08:47
Worklog Time Spent: 10m
Work Description: SourabhBadhya commented on PR #4180:
URL: https://github.com/apache/hive/pull/4180#issuecomment-1517492367
@saihemanth-cloudera @nrg4878 @abstractdog @deniskuzZ @veghlaci05 @ayushtkn
Can you please review this?
cc @TuroczyX
Issue Time Tracking
-------------------
Worklog Id: (was: 858390)
Time Spent: 3h 10m (was: 3h)
> Inconsistency between session Hive and thread-local Hive may cause HS2
> deadlock
> -------------------------------------------------------------------------------
>
> Key: HIVE-27201
> URL: https://issues.apache.org/jira/browse/HIVE-27201
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> The HiveServer2’s server handler can switch to process the operation from
> other session, in such case, the Hive cached in ThreadLocal is not the same
> as the Hive in SessionState, and can be referenced by another session.
> If the two handlers swap their sessions to process the DatabaseMetaData
> request, and the HiveMetastoreClientFactory obtains the Hive via Hive.get(),
> then there is a chance that the deadlock can happen.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
