[jira] [Closed] (CURATOR-280) LeaderLatch doesn't work when using a zookeeper chroot

[ https://issues.apache.org/jira/browse/CURATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-280. -- Resolution: Duplicate > LeaderLatch doesn't work when using a zookeeper chroot > -

[jira] [Commented] (CURATOR-357) creatingParentsIfNeeded do not create "/"

[ https://issues.apache.org/jira/browse/CURATOR-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721295#comment-17721295 ] Kezhu Wang commented on CURATOR-357: After go through CURATOR-280, I think we should

[jira] [Updated] (CURATOR-357) creatingParentsIfNeeded do not create "/"

[ https://issues.apache.org/jira/browse/CURATOR-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang updated CURATOR-357: --- Issue Type: New Feature (was: Bug) > creatingParentsIfNeeded do not create "/" > --

[jira] [Closed] (CURATOR-357) creatingParentsIfNeeded do not create "/"

[ https://issues.apache.org/jira/browse/CURATOR-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-357. -- Resolution: Won't Fix > creatingParentsIfNeeded do not create "/" > --

[jira] [Closed] (CURATOR-433) Test/Validate Curator with Java 11

[ https://issues.apache.org/jira/browse/CURATOR-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-433. -- Assignee: (was: Kezhu Wang) Resolution: Abandoned We already have ci for Java 11 and Java 17

[jira] [Closed] (CURATOR-196) this.client.create().creatingParentsIfNeeded() throw Puzzling EXCEPTION

[ https://issues.apache.org/jira/browse/CURATOR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-196. -- Resolution: Not A Problem {{NodeExistException}} is expected if target node exists. You can resort to

[jira] [Assigned] (CURATOR-7) Session ids not preserved if EnsembleProvider has changed the ensemble

[ https://issues.apache.org/jira/browse/CURATOR-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang reassigned CURATOR-7: Assignee: Kezhu Wang > Session ids not preserved if EnsembleProvider has changed the ensemble > ---

[jira] [Closed] (CURATOR-7) Session ids not preserved if EnsembleProvider has changed the ensemble

[ https://issues.apache.org/jira/browse/CURATOR-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-7. Fix Version/s: (was: awaiting-response) Assignee: Jordan Zimmerman (was: Kezhu Wang) Res

[jira] [Closed] (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 using d

[ https://issues.apache.org/jira/browse/CURATOR-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-293. -- Resolution: Not A Problem It has been fixed by ZOOKEEPER-1576 which shipped in 3.5.0 and Curator 2.9.1

[jira] [Closed] (CURATOR-655) Working Instagram Hack no human verification ios

[ https://issues.apache.org/jira/browse/CURATOR-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-655. -- Assignee: (was: Jordan Zimmerman) Resolution: Invalid > Working Instagram Hack no human veri

[jira] [Closed] (CURATOR-647) Cannot build 5.3.0: IllegalThreadState with TestTreeCache Test

[ https://issues.apache.org/jira/browse/CURATOR-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-647. -- Resolution: Not A Bug Some tests are flaky. And {{TestTreeCache.testIsolatedThreadGroup}} has been de

[jira] [Closed] (CURATOR-50) CreateBuilderImpl fails on forPath if connectString features a chroot that does not already exist.

[ https://issues.apache.org/jira/browse/CURATOR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-50. - Fix Version/s: (was: TBD) Resolution: Won't Fix > CreateBuilderImpl fails on forPath if connec

[jira] [Assigned] (CURATOR-269) InterProcessSemaphoreV2: decrease level of logging when path not found

[ https://issues.apache.org/jira/browse/CURATOR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang reassigned CURATOR-269: -- Assignee: Kezhu Wang (was: Jordan Zimmerman) > InterProcessSemaphoreV2: decrease level of lo

[jira] [Closed] (CURATOR-32) Improve javadocs around create/setData

[ https://issues.apache.org/jira/browse/CURATOR-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-32. - Fix Version/s: (was: awaiting-response) Resolution: Won't Fix {{CuratorFramework}} is "Zookeep

[jira] [Closed] (CURATOR-115) delayeddistributedqueue failed to sort children

[ https://issues.apache.org/jira/browse/CURATOR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-115. -- Resolution: Fixed After a look for the pr [apache/curator#13|https://github.com/apache/curator/pull/1

[jira] [Closed] (CURATOR-112) ExhibitorEnsembleProvider / ExhibitorRestClient dont support basic auth

[ https://issues.apache.org/jira/browse/CURATOR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-112. -- Fix Version/s: (was: TBD) Resolution: Abandoned These two classes has been deleted in upgra

[jira] [Closed] (CURATOR-205) Repeated InterruptedExceptions during mutex acquire leads to LeaderSelector deadlock

[ https://issues.apache.org/jira/browse/CURATOR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-205. -- Resolution: Duplicate > Repeated InterruptedExceptions during mutex acquire leads to LeaderSelector >

[jira] [Closed] (CURATOR-385) Synchronize startup of ExhibitorEnsembleProvider and Zookeeper connection

[ https://issues.apache.org/jira/browse/CURATOR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-385. -- Resolution: Abandoned This class has been deleted in upgrading to 5.0.0. See Curator-558. > Synchroni

[jira] [Closed] (CURATOR-486) InterProcessMutex.release fails to remove a lock on retries.

[ https://issues.apache.org/jira/browse/CURATOR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-486. -- Resolution: Not A Problem Curator uses {{Guaranteeable.guaranteed}} in deleting lock path. In case of

[jira] [Closed] (CURATOR-629) curator 5.2.0 recipes : client event notify service is single thread

[ https://issues.apache.org/jira/browse/CURATOR-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-629. -- Assignee: (was: Jordan Zimmerman) Resolution: Not A Problem Most framework uses single threa

[jira] [Closed] (CURATOR-184) Background retry doesn't stop with LOST event

[ https://issues.apache.org/jira/browse/CURATOR-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang closed CURATOR-184. -- Resolution: Not A Problem It is by design unless {{CuratorFramework.close}} is called. You can custom