[jira] [Commented] (CURATOR-293) Curator can NOT reconnect after connection lost and session expired when the connection come up while the DNS server is not ready yet.(zookeeper connection string usin

[ https://issues.apache.org/jira/browse/CURATOR-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215159#comment-15215159 ] Jordan Zimmerman commented on CURATOR-293: -- Curator does try to reconnect when there's a

[jira] [Updated] (CURATOR-225) Add a new mode ErrorMode.KEEP

[ https://issues.apache.org/jira/browse/CURATOR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-225: - Priority: Minor (was: Critical) > Add a new mode ErrorMode.KEEP >

[jira] [Commented] (CURATOR-310) Race in PersistentNode startup

[ https://issues.apache.org/jira/browse/CURATOR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215221#comment-15215221 ] ASF GitHub Bot commented on CURATOR-310: GitHub user Randgalt opened a pull request:

[jira] [Updated] (CURATOR-304) Support Sequential Nodes in ServiceDiscovery

[ https://issues.apache.org/jira/browse/CURATOR-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-304: - Fix Version/s: (was: awaiting-response) 3.1.1

Build failed in Jenkins: Curator » Curator Framework #971

See -- [INFO] [INFO] [INFO]

[GitHub] curator pull request: CURATOR-225: Added new ErrorMode value KEEP.

Github user Randgalt commented on the pull request: https://github.com/apache/curator/pull/85#issuecomment-202646917 @zzcoder any updates on this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[jira] [Updated] (CURATOR-225) Add a new mode ErrorMode.KEEP

[ https://issues.apache.org/jira/browse/CURATOR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-225: - Fix Version/s: awaiting-response > Add a new mode ErrorMode.KEEP >

[jira] [Updated] (CURATOR-308) SimpleDistributedQueue::take() hangs if container nodes are removed

[ https://issues.apache.org/jira/browse/CURATOR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-308: - Fix Version/s: 3.1.1 2.10.1 > SimpleDistributedQueue::take() hangs if

[jira] [Assigned] (CURATOR-308) SimpleDistributedQueue::take() hangs if container nodes are removed

[ https://issues.apache.org/jira/browse/CURATOR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman reassigned CURATOR-308: Assignee: Jordan Zimmerman > SimpleDistributedQueue::take() hangs if container

[jira] [Commented] (CURATOR-233) Bug in double barrier

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215169#comment-15215169 ] Jordan Zimmerman commented on CURATOR-233: -- [~mdrob] any status on this? > Bug in double

[jira] [Updated] (CURATOR-308) SimpleDistributedQueue::take() hangs if container nodes are removed

[ https://issues.apache.org/jira/browse/CURATOR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-308: - Fix Version/s: (was: 2.10.1) > SimpleDistributedQueue::take() hangs if container

[jira] [Updated] (CURATOR-312) Memory leak of NamespaceWatcher when register TreeCacheListener to non-existing path

[ https://issues.apache.org/jira/browse/CURATOR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-312: - Assignee: Scott Blum > Memory leak of NamespaceWatcher when register TreeCacheListener

[jira] [Comment Edited] (CURATOR-311) SharedValue could hold stall data when quourm membership changes

[ https://issues.apache.org/jira/browse/CURATOR-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207595#comment-15207595 ] Jian Fang edited comment on CURATOR-311 at 3/28/16 11:51 PM: - I don't have

[jira] [Updated] (CURATOR-307) InterProcessReadWriteLock can throw IndexOutOfBoundsException when connection is lost

[ https://issues.apache.org/jira/browse/CURATOR-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-307: - Fix Version/s: awaiting-response > InterProcessReadWriteLock can throw

[jira] [Commented] (CURATOR-311) SharedValue could hold stall data when quourm membership changes

[ https://issues.apache.org/jira/browse/CURATOR-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215207#comment-15215207 ] Jordan Zimmerman commented on CURATOR-311: -- I was review the SharedValue code and am shocked to

[GitHub] curator pull request: [CURATOR-310] Race in PersistentNode startup

Github user cammckenzie commented on a diff in the pull request: https://github.com/apache/curator/pull/140#discussion_r57663597 --- Diff: curator-recipes/src/main/java/org/apache/curator/framework/recipes/nodes/PersistentNode.java --- @@ -317,6 +317,7 @@ public String

[jira] [Commented] (CURATOR-310) Race in PersistentNode startup

[ https://issues.apache.org/jira/browse/CURATOR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215268#comment-15215268 ] ASF GitHub Bot commented on CURATOR-310: Github user cammckenzie commented on the pull request:

Build failed in Jenkins: Curator-3.0 » Curator Framework #62

See -- [INFO] [INFO]

Build failed in Jenkins: Curator-3.0 #62

See Changes: [nir.dothan] Added a new DYNAMIC_SEQUENTIAL ServiceType which creates an [nir.dothan] added validation for DYNAMIC_SEQUENTIAL service type added a break in [nir.dothan] added an enum method to indicate if a

Jenkins build is back to stable : Curator-3.0 » Curator Recipes #62

See

[jira] [Commented] (CURATOR-312) Memory leak of NamespaceWatcher when register TreeCacheListener to non-existing path

[ https://issues.apache.org/jira/browse/CURATOR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215383#comment-15215383 ] Pavan Kumar M S commented on CURATOR-312: - Sure, i cross verified with version 2.10.0 and

[jira] [Resolved] (CURATOR-312) Memory leak of NamespaceWatcher when register TreeCacheListener to non-existing path

[ https://issues.apache.org/jira/browse/CURATOR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavan Kumar M S resolved CURATOR-312. - Resolution: Fixed > Memory leak of NamespaceWatcher when register TreeCacheListener to

[GitHub] curator pull request: [CURATOR-310] Race in PersistentNode startup

Github user cammckenzie commented on the pull request: https://github.com/apache/curator/pull/140#issuecomment-202669736 Looks OK to me. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] curator pull request: [CURATOR-310] Race in PersistentNode startup

Github user Randgalt commented on a diff in the pull request: https://github.com/apache/curator/pull/140#discussion_r57663645 --- Diff: curator-recipes/src/main/java/org/apache/curator/framework/recipes/nodes/PersistentNode.java --- @@ -317,6 +317,7 @@ public String

[GitHub] curator pull request: [CURATOR-310] Race in PersistentNode startup

Github user cammckenzie commented on a diff in the pull request: https://github.com/apache/curator/pull/140#discussion_r57663793 --- Diff: curator-recipes/src/main/java/org/apache/curator/framework/recipes/nodes/PersistentNode.java --- @@ -317,6 +317,7 @@ public String

[jira] [Commented] (CURATOR-310) Race in PersistentNode startup

[ https://issues.apache.org/jira/browse/CURATOR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215261#comment-15215261 ] ASF GitHub Bot commented on CURATOR-310: Github user Randgalt commented on a diff in the pull

[GitHub] curator pull request: [CURATOR-310] Race in PersistentNode startup

Github user Randgalt commented on the pull request: https://github.com/apache/curator/pull/140#issuecomment-202669627 I updated the method doc. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[jira] [Commented] (CURATOR-310) Race in PersistentNode startup

[ https://issues.apache.org/jira/browse/CURATOR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215283#comment-15215283 ] ASF GitHub Bot commented on CURATOR-310: Github user cammckenzie commented on the pull request:

[jira] [Commented] (CURATOR-310) Race in PersistentNode startup

[ https://issues.apache.org/jira/browse/CURATOR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215280#comment-15215280 ] ASF GitHub Bot commented on CURATOR-310: Github user Randgalt commented on the pull request:

[jira] [Commented] (CURATOR-310) Race in PersistentNode startup

[ https://issues.apache.org/jira/browse/CURATOR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215266#comment-15215266 ] ASF GitHub Bot commented on CURATOR-310: Github user cammckenzie commented on a diff in the pull

[GitHub] curator pull request: [CURATOR-310] Race in PersistentNode startup

Github user cammckenzie commented on the pull request: https://github.com/apache/curator/pull/140#issuecomment-202668460 Looks like an OK short fix to me. We probably need to document the new contract (call waitForInitialCreate before calling setData) somewhere? --- If your project