You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Denys Kuzmenko (Jira)" <ji...@apache.org> on 2023/04/25 08:31:00 UTC

[jira] [Commented] (HIVE-27201) Inconsistency between session Hive and thread-local Hive may cause HS2 deadlock

    [ https://issues.apache.org/jira/browse/HIVE-27201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716165#comment-17716165 ] 

Denys Kuzmenko commented on HIVE-27201:
---------------------------------------

Merged to master.
Thanks [~dengzh] for the patch and [~gsaihemanth] for the review!

> 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: 7h 20m
>  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)