zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-3471) Potential lock unavailable due to dangling ephemeral nodes left during local session upgrading
Date Sun, 28 Jul 2019 18:08:00 GMT

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

ASF GitHub Bot updated ZOOKEEPER-3471:
--------------------------------------
    Labels: pull-request-available  (was: )

> 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
>
>
> 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
(v7.6.14#76016)

Mime
View raw message