[jira] [Commented] (CURATOR-544) Implement SessionConnectionHandlingPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940355#comment-16940355 ] Zili Chen commented on CURATOR-544: --- Thanks for your participation [~shayshim]! I think it does meet

[jira] [Commented] (CURATOR-544) Implement SessionConnectionHandlingPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940315#comment-16940315 ] Zili Chen commented on CURATOR-544: --- Since the only different is {{callWithRetry}} I even think of

[jira] [Commented] (CURATOR-544) Implement SessionConnectionHandlingPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940358#comment-16940358 ] Zili Chen commented on CURATOR-544: --- Oops I mean the email linked above. In fact the discussion in

[jira] [Commented] (CURATOR-544) Implement SessionConnectionHandlingPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940404#comment-16940404 ] Zili Chen commented on CURATOR-544: --- [~shayshim] You are right. It seems I mess up other threads here

[jira] [Created] (CURATOR-544) Implement SessionConnectionHandlingPolicy

Zili Chen created CURATOR-544: - Summary: Implement SessionConnectionHandlingPolicy Key: CURATOR-544 URL: https://issues.apache.org/jira/browse/CURATOR-544 Project: Apache Curator Issue Type: New

[jira] [Commented] (CURATOR-544) Implement SessionConnectionHandlingPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046693#comment-17046693 ] Zili Chen commented on CURATOR-544: --- [~randgalt] I just notice that we don't rely on {{RetryLoop}}

[jira] [Commented] (CURATOR-544) Implement SessionConnectionHandlingPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041703#comment-17041703 ] Zili Chen commented on CURATOR-544: --- [~shayshim] [~randgalt] it happens I have time to work on this

[jira] [Created] (CURATOR-562) Remove ConnectionHandlingPolicy

Zili Chen created CURATOR-562: - Summary: Remove ConnectionHandlingPolicy Key: CURATOR-562 URL: https://issues.apache.org/jira/browse/CURATOR-562 Project: Apache Curator Issue Type: Improvement

[jira] [Updated] (CURATOR-544) Implement SessionFailedRetryPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-544: -- Description:

[jira] [Updated] (CURATOR-544) Implement SessionFailedRetryPolicy

[ https://issues.apache.org/jira/browse/CURATOR-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-544: -- Summary: Implement SessionFailedRetryPolicy (was: Implement SessionConnectionHandlingPolicy) >

[jira] [Closed] (CURATOR-581) Possible malformed OSGi export pattern

[ https://issues.apache.org/jira/browse/CURATOR-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-581. - Assignee: Zili Chen (was: Jordan Zimmerman) Resolution: Fixed closed by 

[jira] [Closed] (CURATOR-583) Fix ArrayIndexOutOfBoundsException when passing empty list parameter to reconfigure API

[ https://issues.apache.org/jira/browse/CURATOR-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-583. - Resolution: Fixed master via 800fdf4c5cbe3f0e3cebc64357707ba743fc46e2 > Fix

[jira] [Created] (CURATOR-581) Possible malformed OSGi export pattern

Zili Chen created CURATOR-581: - Summary: Possible malformed OSGi export pattern Key: CURATOR-581 URL: https://issues.apache.org/jira/browse/CURATOR-581 Project: Apache Curator Issue Type:

[jira] [Commented] (CURATOR-581) Possible malformed OSGi export pattern

[ https://issues.apache.org/jira/browse/CURATOR-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173796#comment-17173796 ] Zili Chen commented on CURATOR-581: --- Hi [~acosentino] [~skitching], I believe this issue would benefit

[jira] [Commented] (CURATOR-613) please implement setAcl Command -R option !!!

[ https://issues.apache.org/jira/browse/CURATOR-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17409346#comment-17409346 ] Zili Chen commented on CURATOR-613: --- [~startjava] do you mean setACL recursive on path? > please

[jira] [Created] (CURATOR-619) Replace OutstandingOps with JDK bundled Phaser

Zili Chen created CURATOR-619: - Summary: Replace OutstandingOps with JDK bundled Phaser Key: CURATOR-619 URL: https://issues.apache.org/jira/browse/CURATOR-619 Project: Apache Curator Issue

[jira] [Commented] (CURATOR-619) Replace OutstandingOps with JDK bundled Phaser

[ https://issues.apache.org/jira/browse/CURATOR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429552#comment-17429552 ] Zili Chen commented on CURATOR-619: --- master via 1038aa6d03f240fb8a8de9736adc51ccbcc9f5b6 Thanks for

[jira] [Closed] (CURATOR-633) Run org.apache.curator.framework.state.TestConnectionStateManager#testConnectionStateRecoversFromUnexpectedExpiredConnection only for Zookeeper 3.6.x

[ https://issues.apache.org/jira/browse/CURATOR-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-633. - Assignee: Zili Chen (was: Jordan Zimmerman) Resolution: Fixed master via

[jira] [Assigned] (CURATOR-630) Upgrade jetty to 9.4.latest

[ https://issues.apache.org/jira/browse/CURATOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-630: - Assignee: (was: Zili Chen) > Upgrade jetty to 9.4.latest > --- > >

[jira] [Assigned] (CURATOR-630) Upgrade jetty to 9.4.latest

[ https://issues.apache.org/jira/browse/CURATOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-630: - Assignee: Zili Chen > Upgrade jetty to 9.4.latest > --- > >

[jira] [Closed] (CURATOR-624) Migrate CI from Travis to GitHub actions

[ https://issues.apache.org/jira/browse/CURATOR-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-624. - > Migrate CI from Travis to GitHub actions > > >

[jira] [Resolved] (CURATOR-624) Migrate CI from Travis to GitHub actions

[ https://issues.apache.org/jira/browse/CURATOR-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-624. --- Resolution: Fixed As far as I can see, current master contains GitHub Actions only. Closed as

[jira] [Commented] (CURATOR-630) Upgrade jetty to 9.4.latest

[ https://issues.apache.org/jira/browse/CURATOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514654#comment-17514654 ] Zili Chen commented on CURATOR-630: --- I think the setting of Curator prevents assigning people out of

[jira] [Closed] (CURATOR-630) Upgrade jetty to 9.4.latest

[ https://issues.apache.org/jira/browse/CURATOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-630. - Resolution: Fixed Closed via 5ca31e3520189fac3c0447e3083a76756a535723. > Upgrade jetty to 9.4.latest >

[jira] [Updated] (CURATOR-521) LeaderLatch closed with CloseMode=null does not close

[ https://issues.apache.org/jira/browse/CURATOR-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-521: -- Fix Version/s: (was: 5.6.0) > LeaderLatch closed with CloseMode=null does not close >

[jira] [Commented] (CURATOR-521) LeaderLatch closed with CloseMode=null does not close

[ https://issues.apache.org/jira/browse/CURATOR-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765657#comment-17765657 ] Zili Chen commented on CURATOR-521: --- But I agree we can somehow improve the code quality here to avoid

[jira] [Resolved] (CURATOR-521) LeaderLatch closed with CloseMode=null does not close

[ https://issues.apache.org/jira/browse/CURATOR-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-521. --- Assignee: Zili Chen (was: Kezhu Wang) Resolution: Invalid No. We check closeMode is not null

[jira] [Assigned] (CURATOR-690) CuratorCache fails to load the cache if there are more than 64K child ZNodes

[ https://issues.apache.org/jira/browse/CURATOR-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-690: - Assignee: Zili Chen > CuratorCache fails to load the cache if there are more than 64K child

[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=17765408#comment-17765408 ] Zili Chen commented on CURATOR-508: --- After a closer look the issued call above is with a {{null}}

[jira] [Closed] (CURATOR-513) Add sorted() to GetChildrenBuilder

[ https://issues.apache.org/jira/browse/CURATOR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-513. - Resolution: Won't Fix See comment above. This is trivial to sort after getting the result. We don't

[jira] [Commented] (CURATOR-689) Guard create/setData/delete with lock path

[ https://issues.apache.org/jira/browse/CURATOR-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765410#comment-17765410 ] Zili Chen commented on CURATOR-689: --- There is a related discussion at

[jira] [Comment Edited] (CURATOR-689) Guard create/setData/delete with lock path

[ https://issues.apache.org/jira/browse/CURATOR-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765410#comment-17765410 ] Zili Chen edited comment on CURATOR-689 at 9/15/23 1:21 AM: There is a

[jira] [Resolved] (CURATOR-690) CuratorCache fails to load the cache if there are more than 64K child ZNodes

[ https://issues.apache.org/jira/browse/CURATOR-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-690. --- Resolution: Fixed master via 51483adb1d1dd3e43812b5d0ec7c03b6d1d05c7c > CuratorCache fails to load

[jira] [Closed] (CURATOR-532) Manually configurable ZooKeeper 3.4.x compatibility

[ https://issues.apache.org/jira/browse/CURATOR-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-532. - Resolution: Won't Fix ZK 3.4 is not supported and the abstract proposal gets no feedback. > Manually

[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 ] Zili Chen closed CURATOR-508. - Assignee: Zili Chen Resolution: Not A Bug > LeaderLatch#setNode might throws unexpected

[jira] [Created] (CURATOR-691) Compatible with JDK 21

Zili Chen created CURATOR-691: - Summary: Compatible with JDK 21 Key: CURATOR-691 URL: https://issues.apache.org/jira/browse/CURATOR-691 Project: Apache Curator Issue Type: Bug

[jira] [Created] (CURATOR-692) Remove mockito dependencies

Zili Chen created CURATOR-692: - Summary: Remove mockito dependencies Key: CURATOR-692 URL: https://issues.apache.org/jira/browse/CURATOR-692 Project: Apache Curator Issue Type: Sub-task

[jira] [Work started] (CURATOR-692) Remove mockito dependencies

[ https://issues.apache.org/jira/browse/CURATOR-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CURATOR-692 started by Zili Chen. - > Remove mockito dependencies > --- > > Key:

[jira] [Reopened] (CURATOR-521) LeaderLatch closed with CloseMode=null does not close

[ https://issues.apache.org/jira/browse/CURATOR-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reopened CURATOR-521: --- Sorry, I just found that we have a {{public void close(CloseMode closeMode)}} method that can pass

[jira] [Resolved] (CURATOR-521) LeaderLatch closed with CloseMode=null does not close

[ https://issues.apache.org/jira/browse/CURATOR-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-521. --- Resolution: Fixed master via 3468ee91561534d5a748bfb06902725542d07347 > LeaderLatch closed with

[jira] [Resolved] (CURATOR-691) Compatible with JDK 21

[ https://issues.apache.org/jira/browse/CURATOR-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-691. --- Resolution: Fixed master via a83a0b2e5590f1961439e48be86e34ace39e5979 > Compatible with JDK 21 >

[jira] [Resolved] (CURATOR-693) Bump zookeepeer to 3.7.2

[ https://issues.apache.org/jira/browse/CURATOR-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-693. --- Assignee: Zili Chen (was: Enrico Olivelli) Resolution: Fixed master via

[jira] [Updated] (CURATOR-691) Compatible with JDK 21

[ https://issues.apache.org/jira/browse/CURATOR-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-691: -- Fix Version/s: 5.6.0 > Compatible with JDK 21 > -- > > Key:

[jira] [Updated] (CURATOR-693) Bump zookeepeer to 3.7.2

[ https://issues.apache.org/jira/browse/CURATOR-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-693: -- Fix Version/s: 5.6.0 > Bump zookeepeer to 3.7.2 > > > Key:

[jira] [Resolved] (CURATOR-692) Remove mockito dependencies

[ https://issues.apache.org/jira/browse/CURATOR-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-692. --- Resolution: Fixed master via 2a94b2d7971bf47c2c12554bcd4c2e95581f607a > Remove mockito

[jira] [Updated] (CURATOR-504) Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-504: -- Fix Version/s: 5.4.0 (was: 5.5.0) > Race conditions in LeaderLatch after

[jira] [Resolved] (CURATOR-504) Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-504. --- Resolution: Fixed > Race conditions in LeaderLatch after reconnecting to ensemble >

[jira] [Updated] (CURATOR-504) Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-504: -- Fix Version/s: 5.5.0 > Race conditions in LeaderLatch after reconnecting to ensemble >

[jira] [Reopened] (CURATOR-504) Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reopened CURATOR-504: --- Assignee: Zili Chen (was: Jordan Zimmerman) > Race conditions in LeaderLatch after reconnecting

[jira] [Created] (CURATOR-685) Cleanup docs and setups for the old site deployment in the main repo

Zili Chen created CURATOR-685: - Summary: Cleanup docs and setups for the old site deployment in the main repo Key: CURATOR-685 URL: https://issues.apache.org/jira/browse/CURATOR-685 Project: Apache

[jira] [Closed] (CURATOR-685) Cleanup docs and setups for the old site deployment in the main repo

[ https://issues.apache.org/jira/browse/CURATOR-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-685. - Resolution: Fixed master via ec7759317d3e0bcdc7d6220f01297dc522184b17 > Cleanup docs and setups for

[jira] [Closed] (CURATOR-586) NamespaceFacade return null if namespace is empty

[ https://issues.apache.org/jira/browse/CURATOR-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-586. - Resolution: Not A Problem > NamespaceFacade return null if namespace is empty >

[jira] [Commented] (CURATOR-640) IllegalThreadStateException thrown when access PathChildrenCache in different thread groups

[ https://issues.apache.org/jira/browse/CURATOR-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543455#comment-17543455 ] Zili Chen commented on CURATOR-640: --- Thanks for reporting this issue [~shixg]! I've add a test and

[jira] [Assigned] (CURATOR-640) IllegalThreadStateException thrown when access PathChildrenCache in different thread groups

[ https://issues.apache.org/jira/browse/CURATOR-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-640: - Assignee: Zili Chen > IllegalThreadStateException thrown when access PathChildrenCache in

[jira] [Closed] (CURATOR-514) Utilize ThreadLocalRandom In QueueSharder

[ https://issues.apache.org/jira/browse/CURATOR-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-514. - Resolution: Fixed Resolved in master via f44ff8844f0727e155d7f8e8e6172757acc060cd. > Utilize

[jira] [Updated] (CURATOR-646) Fix RAT failure reports and add a CI task to prevent regression

[ https://issues.apache.org/jira/browse/CURATOR-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-646: -- Fix Version/s: 5.4.0 > Fix RAT failure reports and add a CI task to prevent regression >

[jira] [Closed] (CURATOR-646) Fix RAT failure reports and add a CI task to prevent regression

[ https://issues.apache.org/jira/browse/CURATOR-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-646. - Resolution: Fixed master via fd5dc4bd8ed3ea973b3063ad11ccaeeff7238883 > Fix RAT failure reports and

[jira] [Created] (CURATOR-646) Fix RAT failure reports and add a CI task to prevent regression

Zili Chen created CURATOR-646: - Summary: Fix RAT failure reports and add a CI task to prevent regression Key: CURATOR-646 URL: https://issues.apache.org/jira/browse/CURATOR-646 Project: Apache Curator

[jira] [Commented] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17559237#comment-17559237 ] Zili Chen commented on CURATOR-644: --- [~rikimberley] OK. I can see that there're possibly two

[jira] [Updated] (CURATOR-609) ModeledCache attempts to deserialize empty ZNodes on deletion, resulting in exceptions

[ https://issues.apache.org/jira/browse/CURATOR-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-609: -- Fix Version/s: 5.4.0 (was: 5.2.2) > ModeledCache attempts to deserialize empty

[jira] [Updated] (CURATOR-643) Adds possibility to disable automatic parent creation for PersistentTtlNode

[ https://issues.apache.org/jira/browse/CURATOR-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-643: -- Fix Version/s: 5.3.0 > Adds possibility to disable automatic parent creation for PersistentTtlNode >

[jira] [Updated] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-644: -- Description: Clone from CURATOR-504. We use LeaderLatch in a lot of places in our system and when

[jira] [Commented] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558901#comment-17558901 ] Zili Chen commented on CURATOR-644: --- Still I don't see the relation between this issue and Curator.

[jira] [Resolved] (CURATOR-643) Adds possibility to disable automatic parent creation for PersistentTtlNode

[ https://issues.apache.org/jira/browse/CURATOR-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-643. --- Assignee: Zili Chen Resolution: Fixed master via f4abf511c6fc514aae41ed75deb2483bf9726f24 >

[jira] [Closed] (CURATOR-3) LeaderLatch race condition causing extra nodes to be added in Zookeeper Edit

[ https://issues.apache.org/jira/browse/CURATOR-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-3. --- Fix Version/s: (was: TBD) Resolution: Invalid Invalid in 5.2.1. > LeaderLatch race condition

[jira] [Closed] (CURATOR-641) 死锁 deadlock

[ https://issues.apache.org/jira/browse/CURATOR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-641. - Resolution: Invalid There is not a method named "watcher" for LockInternals. Also it would be better

[jira] [Commented] (CURATOR-3) LeaderLatch race condition causing extra nodes to be added in Zookeeper Edit

[ https://issues.apache.org/jira/browse/CURATOR-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558880#comment-17558880 ] Zili Chen commented on CURATOR-3: - After some reasoning I think this issue won't happen in 5.2.1. # close

[jira] [Commented] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558889#comment-17558889 ] Zili Chen commented on CURATOR-644: --- [~randgalt] [~rikimberley] It seems a desired behavior that if

[jira] [Updated] (CURATOR-638) Curator disconnect from zookeeper when IPs change

[ https://issues.apache.org/jira/browse/CURATOR-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-638: -- Fix Version/s: 5.4.0 > Curator disconnect from zookeeper when IPs change >

[jira] [Updated] (CURATOR-578) EnsembleTracker replace hostname connectString with wrong ip from zk config

[ https://issues.apache.org/jira/browse/CURATOR-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-578: -- Fix Version/s: 5.4.0 > EnsembleTracker replace hostname connectString with wrong ip from zk config >

[jira] [Updated] (CURATOR-623) DistributedQueue stops filling after long disconnect from cluster

[ https://issues.apache.org/jira/browse/CURATOR-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-623: -- Fix Version/s: 5.3.0 > DistributedQueue stops filling after long disconnect from cluster >

[jira] [Reopened] (CURATOR-514) Utilize ThreadLocalRandom In QueueSharder

[ https://issues.apache.org/jira/browse/CURATOR-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reopened CURATOR-514: --- To add fixed version. > Utilize ThreadLocalRandom In QueueSharder >

[jira] [Commented] (CURATOR-645) LeaderLatch generates infinite loop with two LeaderLatch instances competing for the leadership

[ https://issues.apache.org/jira/browse/CURATOR-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17561094#comment-17561094 ] Zili Chen commented on CURATOR-645: --- I ever left a comment in the initial commit that we may call

[jira] [Updated] (CURATOR-640) IllegalThreadStateException thrown when access PathChildrenCache in different thread groups

[ https://issues.apache.org/jira/browse/CURATOR-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-640: -- Fix Version/s: 5.3.0 > IllegalThreadStateException thrown when access PathChildrenCache in different

[jira] [Resolved] (CURATOR-514) Utilize ThreadLocalRandom In QueueSharder

[ https://issues.apache.org/jira/browse/CURATOR-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-514. --- Resolution: Fixed > Utilize ThreadLocalRandom In QueueSharder >

[jira] [Updated] (CURATOR-514) Utilize ThreadLocalRandom In QueueSharder

[ https://issues.apache.org/jira/browse/CURATOR-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-514: -- Fix Version/s: 5.3.0 > Utilize ThreadLocalRandom In QueueSharder >

[jira] [Resolved] (CURATOR-640) IllegalThreadStateException thrown when access PathChildrenCache in different thread groups

[ https://issues.apache.org/jira/browse/CURATOR-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-640. --- Resolution: Fixed master via 83de54888d39173acd7ddad0435f955e4ba736b1 >

[jira] [Resolved] (CURATOR-623) DistributedQueue stops filling after long disconnect from cluster

[ https://issues.apache.org/jira/browse/CURATOR-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-623. --- Resolution: Fixed master via d58aa73f4cc78325abb2ae0ffd95fd9cf0776541 > DistributedQueue stops

[jira] [Closed] (CURATOR-516) Remove Deprecated newSetFromMap

[ https://issues.apache.org/jira/browse/CURATOR-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-516. - Resolution: Not A Problem Closed as Not A Problem. > Remove Deprecated newSetFromMap >

[jira] [Updated] (CURATOR-642) Upgrade Guava to 31.1

[ https://issues.apache.org/jira/browse/CURATOR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-642: -- Fix Version/s: 5.4.0 > Upgrade Guava to 31.1 > - > > Key:

[jira] [Resolved] (CURATOR-642) Upgrade Guava to 31.1

[ https://issues.apache.org/jira/browse/CURATOR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-642. --- Resolution: Fixed Master via 4baec84f89b4e965460895ac666e7b06a0b9a10b > Upgrade Guava to 31.1 >

[jira] [Commented] (CURATOR-645) LeaderLatch generates infinite loop with two LeaderLatch instances competing for the leadership

[ https://issues.apache.org/jira/browse/CURATOR-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566107#comment-17566107 ] Zili Chen commented on CURATOR-645: --- I push a patch at [https://github.com/apache/curator/pull/430.]

[jira] [Commented] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566108#comment-17566108 ] Zili Chen commented on CURATOR-644: --- [~rikimberley] I push a patch here:

[jira] [Commented] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566136#comment-17566136 ] Zili Chen commented on CURATOR-644: --- UPDATE - I believe that patch should resolve this ticket now.

[jira] [Commented] (CURATOR-504) Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566146#comment-17566146 ] Zili Chen commented on CURATOR-504: --- I prepare a patch to release this situation in

[jira] [Comment Edited] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566108#comment-17566108 ] Zili Chen edited comment on CURATOR-644 at 7/13/22 2:29 AM: [~rikimberley] I

[jira] [Comment Edited] (CURATOR-645) LeaderLatch generates infinite loop with two LeaderLatch instances competing for the leadership

[ https://issues.apache.org/jira/browse/CURATOR-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566107#comment-17566107 ] Zili Chen edited comment on CURATOR-645 at 7/13/22 2:29 AM: I push a patch

[jira] [Comment Edited] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566108#comment-17566108 ] Zili Chen edited comment on CURATOR-644 at 7/13/22 2:28 AM: [~rikimberley] I

[jira] [Commented] (CURATOR-644) CLONE - Race conditions in LeaderLatch after reconnecting to ensemble

[ https://issues.apache.org/jira/browse/CURATOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569212#comment-17569212 ] Zili Chen commented on CURATOR-644: --- Hi [~rikimberley], 1. Could you run a hotfix version on your

[jira] [Commented] (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:comment-tabpanel=17567570#comment-17567570 ] Zili Chen commented on CURATOR-307: --- Thank [~kezhuw] to give the insight. I believe this issue should

[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 ] Zili Chen updated CURATOR-307: -- Fix Version/s: 2.8.0 > InterProcessReadWriteLock can throw IndexOutOfBoundsException when connection

[jira] [Resolved] (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 ] Zili Chen resolved CURATOR-307. --- Fix Version/s: (was: awaiting-response) Resolution: Fixed > InterProcessReadWriteLock

[jira] [Closed] (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 ] Zili Chen closed CURATOR-307. - > InterProcessReadWriteLock can throw IndexOutOfBoundsException when connection > is lost >

[jira] [Assigned] (CURATOR-524) Apache is asking us to review our build files and make sure we're using https for all URLs.

[ https://issues.apache.org/jira/browse/CURATOR-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-524: - Assignee: Zili Chen > Apache is asking us to review our build files and make sure we're using

[jira] [Commented] (CURATOR-513) Add sorted() to GetChildrenBuilder

[ https://issues.apache.org/jira/browse/CURATOR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17567572#comment-17567572 ] Zili Chen commented on CURATOR-513: --- This may ba a valid improvement but you can also simply sort the

[jira] [Resolved] (CURATOR-523) Use --release flag when compiling on JDK9+

[ https://issues.apache.org/jira/browse/CURATOR-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-523. --- Resolution: Fixed master via db399d4194b55a2b2af7f8c454002f8a11400b87 > Use --release flag when

[jira] [Closed] (CURATOR-523) Use --release flag when compiling on JDK9+

[ https://issues.apache.org/jira/browse/CURATOR-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-523. - > Use --release flag when compiling on JDK9+ > -- > >

[jira] [Updated] (CURATOR-523) Use --release flag when compiling on JDK9+

[ https://issues.apache.org/jira/browse/CURATOR-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-523: -- Issue Type: Improvement (was: Bug) > Use --release flag when compiling on JDK9+ >

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-233: -- Fix Version/s: (was: TBD) > Bug in double barrier > - > >

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-233. - > Bug in double barrier > - > > Key: CURATOR-233 > URL:

  1   2   3   >