distributedlog-dev mailing list archives

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

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

ASF GitHub Bot commented on DL-86:

Github user franckcuny commented on the issue:

    @sijie is this a transient error ? Looks like time out while doing some operation with
ZK, so could be a misconfigured test too.

> 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