[
https://issues.apache.org/jira/browse/HIVE-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283177#comment-14283177
]
Brock Noland commented on HIVE-9119:
------------------------------------
FYI this [broke
TestMTQueries|https://issues.apache.org/jira/browse/HIVE-1869?focusedCommentId=14283175&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14283175].
Fixing in an old jira HIVE-1869 for that class.
> ZooKeeperHiveLockManager does not use zookeeper in the proper way
> -----------------------------------------------------------------
>
> Key: HIVE-9119
> URL: https://issues.apache.org/jira/browse/HIVE-9119
> Project: Hive
> Issue Type: Improvement
> Components: Locking
> Affects Versions: 0.13.0, 0.14.0, 0.13.1
> Reporter: Na Yang
> Assignee: Na Yang
> Labels: TODOC15
> Fix For: 0.15.0
>
> Attachments: HIVE-9119.1.patch, HIVE-9119.2.patch, HIVE-9119.3.patch,
> HIVE-9119.4.patch
>
>
> ZooKeeperHiveLockManager does not use zookeeper in the proper way.
> Currently a new zookeeper client instance is created for each
> getlock/releaselock query which sometimes causes the number of open
> connections between
> HiveServer2 and ZooKeeper exceed the max connection number that zookeeper
> server allows.
> To use zookeeper as a distributed lock, there is no need to create a new
> zookeeper instance for every getlock try. A single zookeeper instance could
> be reused and shared by ZooKeeperHiveLockManagers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
