You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/07/01 10:48:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16876098#comment-16876098 ] 

ASF subversion and git services commented on KYLIN-4039:
--------------------------------------------------------

Commit 8712a872048025d082f1f3e565f39d0f563b785f in kylin's branch refs/heads/master from ZhengshuaiPENG
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=8712a87 ]

KYLIN-4039, fix ZK distributed lock may not release lock when catching interrupt exception


> 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
>
> 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.3#76005)