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

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

Commit 96ba0c66889e0caa29f52c3d740536ef81d8dc5c in kylin's branch 
refs/heads/master from XiaoxiangYu
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=96ba0c6 ]

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

This reverts commit 8712a872048025d082f1f3e565f39d0f563b785f.


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

Reply via email to