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

Posted to issues@hive.apache.org by "J.P Feng (JIRA)" <ji...@apache.org> on 2017/12/25 09:20:00 UTC

[jira] [Updated] (HIVE-18303) ZooKeeperHiveLockManager throws Failed to release ZooKeeper lock Exception

     [ https://issues.apache.org/jira/browse/HIVE-18303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J.P Feng updated HIVE-18303:
----------------------------
    Summary: ZooKeeperHiveLockManager throws Failed to release ZooKeeper lock Exception  (was: ZooKeeperHiveLockManager should close after lock release in releaseLocksAndCommitOrRollback)

> ZooKeeperHiveLockManager throws Failed to release ZooKeeper lock Exception
> --------------------------------------------------------------------------
>
>                 Key: HIVE-18303
>                 URL: https://issues.apache.org/jira/browse/HIVE-18303
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 2.1.1, 2.2.0
>         Environment: jdk 1.7, centos
>            Reporter: J.P Feng
>
> i found exception :
> ZooKeeperHiveLockManager: Failed to release ZooKeeper lock: 
> java.lang.IllegalStateException: instance must be started before calling this method
> because in ShutdownHookManager, priority of CuratorFrameworkSingleton.closeAndReleaseInstance is 10, but in Driver.releaseLocksAndCommitOrRollback, it's 0. So locks are released after CuratorFramework is closed, which may case such exception.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)