curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-7) Session ids not preserved if EnsembleProvider has changed the ensemble
Date Wed, 30 Jul 2014 17:00:41 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079523#comment-14079523
] 

Jordan Zimmerman commented on CURATOR-7:
----------------------------------------

We're trying to keep up. For most of Curator's life I was the only active committer. We're
get more committers, but any help you can provide would be appreciated.

> Session ids not preserved if EnsembleProvider has changed the ensemble
> ----------------------------------------------------------------------
>
>                 Key: CURATOR-7
>                 URL: https://issues.apache.org/jira/browse/CURATOR-7
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Client
>    Affects Versions: 2.0.0-incubating
>            Reporter: Shevek
>             Fix For: awaiting-response
>
>         Attachments: EnsembleProvider-zookeeper-3.5.x.patch
>
>
> See https://github.com/Netflix/curator/issues/266
> InterProcessMutex, LeaderLatch, etc use an ephemeral node. If ZooKeeper gives a Disconnected
event, the native client reconnects with the same session id, and the ephemeral node is preserved.
If the ensemble changes at any point before a Disconnect, Curator's ConnectionState#checkState()
calls handleNewConnectionString(), which constructs a new native ZK client, discarding the
previous session id, and losing all locks.
> This can be expensive.
> Can ConnectionState be made to preserve the session id, or be more conservative about
discarding the entire native client on a Disconnected event?
> Clarifications:
> An ensemble change (e.g. adding a new node to a cluster) does not mean that all session
ids are now invalid. The next network glitch should not break locks.
> There is no assumption in this description that the reconfiguration and the glitch/disconnection
were related - they need not be.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message