[jira] [Work logged] (CURATOR-498) Protected Mode creation can mistake closing session's node causing problems for many recipes such as LeaderLatch

[ https://issues.apache.org/jira/browse/CURATOR-498?focusedWorklogId=202154&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-202154 ] ASF GitHub Bot logged work on CURATOR-498: -- Author: ASF GitHub Bot

[GitHub] Randgalt commented on issue #303: [CURATOR-498] Protected Mode creation can mistake closing session's node causing problems for many recipes such as LeaderLatch

Randgalt commented on issue #303: [CURATOR-498] Protected Mode creation can mistake closing session's node causing problems for many recipes such as LeaderLatch URL: https://github.com/apache/curator/pull/303#issuecomment-466118760 > does Curator 2.x suffer this issue and if so, will we ma

[jira] [Work logged] (CURATOR-498) Protected Mode creation can mistake closing session's node causing problems for many recipes such as LeaderLatch

[ https://issues.apache.org/jira/browse/CURATOR-498?focusedWorklogId=202054&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-202054 ] ASF GitHub Bot logged work on CURATOR-498: -- Author: ASF GitHub Bot

[GitHub] TisonKun commented on issue #303: [CURATOR-498] Protected Mode creation can mistake closing session's node causing problems for many recipes such as LeaderLatch

TisonKun commented on issue #303: [CURATOR-498] Protected Mode creation can mistake closing session's node causing problems for many recipes such as LeaderLatch URL: https://github.com/apache/curator/pull/303#issuecomment-466068928 @Randgalt does Curator 2.x suffer this issue and if so, wi

[jira] [Commented] (CURATOR-508) LeaderLatch#setNode might throws unexpected NoNodeException

[ https://issues.apache.org/jira/browse/CURATOR-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774253#comment-16774253 ] Jordan Zimmerman commented on CURATOR-508: -- This is a known bug that will be fi

[jira] [Reopened] (CURATOR-508) LeaderLatch#setNode might throws unexpected NoNodeException

[ https://issues.apache.org/jira/browse/CURATOR-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman reopened CURATOR-508: -- Actually, I think I misread this initially. I apologize. I'll look into it when I get a c

[jira] [Commented] (CURATOR-508) LeaderLatch#setNode might throws unexpected NoNodeException

[ https://issues.apache.org/jira/browse/CURATOR-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774249#comment-16774249 ] TisonKun commented on CURATOR-508: -- Isn't such case *inside Curator*? Specifically, Cu

[jira] [Closed] (CURATOR-508) LeaderLatch#setNode might throws unexpected NoNodeException

[ 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 Cur

[jira] [Created] (CURATOR-508) LeaderLatch#setNode might throws unexpected NoNodeException

TisonKun created CURATOR-508: Summary: LeaderLatch#setNode might throws unexpected NoNodeException Key: CURATOR-508 URL: https://issues.apache.org/jira/browse/CURATOR-508 Project: Apache Curator