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 GitHub Bot (JIRA)" <ji...@apache.org> on 2019/06/11 05:31: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=16860570#comment-16860570 ] 

ASF GitHub Bot commented on KYLIN-4039:
---------------------------------------

ZhengshuaiPENG commented on pull request #681: KYLIN-4039, fix ZK distributed lock may not release lock when catchin…
URL: https://github.com/apache/kylin/pull/681
 
 
   …g interrupt exception
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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