distributedlog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DL-86) Improve handling of lock conflicts in zk session lock
Date Sat, 17 Dec 2016 07:20:58 GMT

    [ https://issues.apache.org/jira/browse/DL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15756537#comment-15756537

Hudson commented on DL-86:

FAILURE: Integrated in Jenkins build distributedlog-nightly-build #158 (See [https://builds.apache.org/job/distributedlog-nightly-build/158/])
DL-86: Improve handling of lock conflicts in zk session lock (sijie: rev 40df29d9b892c660f6626c92472e6c6b4b52007b)
* (edit) distributedlog-core/src/test/java/com/twitter/distributedlog/lock/TestZKSessionLock.java
* (edit) distributedlog-core/src/main/java/com/twitter/distributedlog/lock/ZKSessionLock.java

> 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

View raw message