hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Na Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-9119) ZooKeeperHiveLockManager does not use zookeeper in the proper way
Date Tue, 06 Jan 2015 20:05:35 GMT

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

Na Yang commented on HIVE-9119:
-------------------------------

Those 3 tests all passed successfully on my local environment with the HIVE-9114.patch applied.
Do not know why it is failing on the build machine. The error logs do not seem to be related
to the ZooKeeperHiveLockManager changes in the patch.  

> 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
>         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)

Mime
View raw message