[
https://issues.apache.org/jira/browse/DL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746633#comment-15746633
]
ASF GitHub Bot commented on DL-86:
----------------------------------
Github user sijie commented on the issue:
https://github.com/apache/incubator-distributedlog/pull/58
@franckcuny I think it is a transient error. The tests passed on travis-ci
but failed on apache jenkins ci.
btw, for now, every pull request will be validated on both travis ci and
apache jenkins. so if one passed it, it typically means it is a transient
failure and should be good. we are only concerned if both of them failed.
> 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)
