[
https://issues.apache.org/jira/browse/ZOOKEEPER-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947859#comment-16947859
]
Hudson commented on ZOOKEEPER-3471:
-----------------------------------
SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #730 (See
[https://builds.apache.org/job/ZooKeeper-trunk/730/])
ZOOKEEPER-3471: Fix potential lock unavailable due to dangling ephemeral
(andor: rev 4951a090d7c946f57ac5ab09b5d48a5d7831001d)
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServer.java
* (edit)
zookeeper-server/src/test/java/org/apache/zookeeper/server/quorum/SessionUpgradeQuorumTest.java
> Potential lock unavailable due to dangling ephemeral nodes left during local
> session upgrading
> ----------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3471
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3471
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.6.0
> Reporter: Fangmin Lv
> Assignee: Fangmin Lv
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> There is a race condition which might be triggered if the client create
> session, upgrading the session with ephemeral node, then immediately issued
> close session request before it's removed from local session tracker.
>
> The close session request will be treated as a local session close request
> since it still exists in the local session tracker, which goes through the ZK
> pipeline and delete the session from both local and global session tracker.
> Since the session is not tracked anymore, it will leave the ephemeral nodes
> there.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
