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

Posted to issues@kylin.apache.org by "nichunen (Jira)" <ji...@apache.org> on 2019/09/17 15:30:00 UTC

[jira] [Updated] (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 updated KYLIN-4039:
----------------------------
    Fix Version/s:     (was: v3.0.0-alpha2)
                   v3.0.0-beta

> 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.2#803003)