[jira] [Resolved] (ZOOKEEPER-3471) Potential lock unavailable due to dangling ephemeral nodes left during local session upgrading

["Andor Molnar (Jira)" <ji...@apache.org>]

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

Andor Molnar resolved ZOOKEEPER-3471.
-------------------------------------
    Resolution: Fixed

Issue resolved by pull request 1025
[https://github.com/apache/zookeeper/pull/1025]

> 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: 1h 20m
>  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)