[jira] [Closed] (KYLIN-4039) ZookeeperDistributedLock may not release lock when unlock operation was interrupted
[ https://issues.apache.org/jira/browse/KYLIN-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nichunen closed KYLIN-4039. --- Resolved in release v3.0.0-beta(2019-10-25) > ZookeeperDistributedLock may not release lock when unlock operation was > interrupted > --- > > Key: KYLIN-4039 > URL: https://issues.apache.org/jira/browse/KYLIN-4039 > Project: Kylin > Issue Type: Bug >Reporter: PENG Zhengshuai >Assignee: PENG Zhengshuai >Priority: Major > Fix For: v3.0.0-beta > > > ZookeeperDistributedLock may hold the lock and not release it when the unlock > operation was interrupted. > Because the unlock operation contains two steps: > 1. peekLock: get the owner of the lock > 2. purgeLock: purge the lock if the owner of the lock is the current client. > If the peekLock step is interrupted, the purgeLock step won't be executed. > Thus the lock won't be released. > Meanwhile, the lock operation should also consider the interrupt cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (KYLIN-4039) ZookeeperDistributedLock may not release lock when unlock operation was interrupted
[ https://issues.apache.org/jira/browse/KYLIN-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nichunen closed KYLIN-4039. --- Resolution: Fixed > ZookeeperDistributedLock may not release lock when unlock operation was > interrupted > --- > > Key: KYLIN-4039 > URL: https://issues.apache.org/jira/browse/KYLIN-4039 > Project: Kylin > Issue Type: Bug >Reporter: PENG Zhengshuai >Assignee: PENG Zhengshuai >Priority: Major > Fix For: v3.0.0-alpha2 > > > ZookeeperDistributedLock may hold the lock and not release it when the unlock > operation was interrupted. > Because the unlock operation contains two steps: > 1. peekLock: get the owner of the lock > 2. purgeLock: purge the lock if the owner of the lock is the current client. > If the peekLock step is interrupted, the purgeLock step won't be executed. > Thus the lock won't be released. > Meanwhile, the lock operation should also consider the interrupt cases. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (KYLIN-4039) ZookeeperDistributedLock may not release lock when unlock operation was interrupted
[ https://issues.apache.org/jira/browse/KYLIN-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI closed KYLIN-4039. --- Resolution: Fixed Resolved in release 3.0.0-alpha2 (2019-07-30) > ZookeeperDistributedLock may not release lock when unlock operation was > interrupted > --- > > Key: KYLIN-4039 > URL: https://issues.apache.org/jira/browse/KYLIN-4039 > Project: Kylin > Issue Type: Bug >Reporter: PENG Zhengshuai >Assignee: PENG Zhengshuai >Priority: Major > Fix For: v3.0.0-alpha2 > > > ZookeeperDistributedLock may hold the lock and not release it when the unlock > operation was interrupted. > Because the unlock operation contains two steps: > 1. peekLock: get the owner of the lock > 2. purgeLock: purge the lock if the owner of the lock is the current client. > If the peekLock step is interrupted, the purgeLock step won't be executed. > Thus the lock won't be released. > Meanwhile, the lock operation should also consider the interrupt cases. -- This message was sent by Atlassian JIRA (v7.6.14#76016)