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

Posted to dev@distributedlog.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2016/12/21 02:19:58 UTC

[jira] [Resolved] (DL-86) Improve handling of lock conflicts in zk session lock

     [ https://issues.apache.org/jira/browse/DL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sijie Guo resolved DL-86.
-------------------------
    Resolution: Fixed

> Improve handling of lock conflicts in zk session lock
> -----------------------------------------------------
>
>                 Key: DL-86
>                 URL: https://issues.apache.org/jira/browse/DL-86
>             Project: DistributedLog
>          Issue Type: Improvement
>          Components: distributedlog-core
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 0.4.0
>
>
> - lock reacquire could happen in foreground and background thread. so use a semaphore to make sure there is only on e      outstanding  acquire operation. and  check if already hold lock before reacquire.
>     - fix handling zk sibling znode logic. as the znode is sequential znode, the name would be different each time. so only    comparing the client id and session id of the znodes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)