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] [Closed] (CURATOR-508) LeaderLatch#setNode might throws unexpected NoNodeException
Date Thu, 21 Feb 2019 15:19:00 GMT

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

Jordan Zimmerman closed CURATOR-508.
------------------------------------
    Resolution: Not A Problem

The performance/resource overhead for LeaderLatch (and other Curator recipes) needed to watch
recipe nodes is not acceptable. Note: we have a Tech Note about this: [https://cwiki.apache.org/confluence/display/CURATOR/TN7] -
Curator "owns" all paths/nodes given to it and it is an error to change/delete those nodes
outside of Curator recipes.

> LeaderLatch#setNode might throws unexpected NoNodeException
> -----------------------------------------------------------
>
>                 Key: CURATOR-508
>                 URL: https://issues.apache.org/jira/browse/CURATOR-508
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>            Reporter: TisonKun
>            Priority: Major
>
> {code:java}
> private void setNode(String newValue) throws Exception
> {
>  String oldPath = ourPath.getAndSet(newValue);
>  if ( oldPath != null )
>  {
>  client.delete().guaranteed().inBackground().forPath(oldPath);
>  }
> }{code}
> What if the election node deleted for some reason, e.g., the session disconnected and
reconnected? Should we use {{#quietly()}} here?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message