[jira] [Reopened] (CURATOR-660) Enable code coverage reporting to SonarQube

[ https://issues.apache.org/jira/browse/CURATOR-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reopened CURATOR-660: --- > Enable code coverage reporting to SonarQube > --- > >

[jira] [Commented] (CURATOR-660) Enable code coverage reporting to SonarQube

[ https://issues.apache.org/jira/browse/CURATOR-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700447#comment-17700447 ] Zili Chen commented on CURATOR-660: --- [~tamaas] [~andor] [~dora.horvath] Many projects have such

[jira] [Closed] (CURATOR-658) Add Support for TLS-enabled TestingZooKeeperMain

[ https://issues.apache.org/jira/browse/CURATOR-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-658. - Assignee: Zili Chen Resolution: Won't Do See

[jira] [Closed] (CURATOR-660) Enable code coverage reporting to SonarQube

[ https://issues.apache.org/jira/browse/CURATOR-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-660. - Assignee: Zili Chen (was: Jordan Zimmerman) Resolution: Won't Do I've never seen codecov work

[jira] [Closed] (CURATOR-661) Cleanup and refactor build and CI settings

[ https://issues.apache.org/jira/browse/CURATOR-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-661. - Resolution: Fixed > Cleanup and refactor build and CI settings >

[jira] [Commented] (CURATOR-661) Cleanup and refactor build and CI settings

[ https://issues.apache.org/jira/browse/CURATOR-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699493#comment-17699493 ] Zili Chen commented on CURATOR-661: --- master via * ff4d9ff361e0baf50554e2d8198ee624f7ec29ee *

[jira] [Closed] (CURATOR-518) Curator. LeaderSelector. Two successive calls to interruptLeadership() will break autoRequeue.

[ https://issues.apache.org/jira/browse/CURATOR-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-518. - Fix Version/s: 5.5.0 Assignee: Zili Chen Resolution: Fixed master via

[jira] [Reopened] (CURATOR-600) ModeledFramework.delete() doesn't use DeleteOptions

[ https://issues.apache.org/jira/browse/CURATOR-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reopened CURATOR-600: --- > ModeledFramework.delete() doesn't use DeleteOptions >

[jira] [Updated] (CURATOR-600) ModeledFramework.delete() doesn't use DeleteOptions

[ https://issues.apache.org/jira/browse/CURATOR-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-600: -- Fix Version/s: 5.5.0 > ModeledFramework.delete() doesn't use DeleteOptions >

[jira] [Closed] (CURATOR-600) ModeledFramework.delete() doesn't use DeleteOptions

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

[jira] [Closed] (CURATOR-600) ModeledFramework.delete() doesn't use DeleteOptions

[ https://issues.apache.org/jira/browse/CURATOR-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-600. - Resolution: Fixed > ModeledFramework.delete() doesn't use DeleteOptions >

[jira] [Created] (CURATOR-661) Cleanup build and CI settings

Zili Chen created CURATOR-661: - Summary: Cleanup build and CI settings Key: CURATOR-661 URL: https://issues.apache.org/jira/browse/CURATOR-661 Project: Apache Curator Issue Type: Improvement

[jira] [Updated] (CURATOR-661) Cleanup and refactor build and CI settings

[ https://issues.apache.org/jira/browse/CURATOR-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-661: -- Summary: Cleanup and refactor build and CI settings (was: Cleanup build and CI settings) > Cleanup

[jira] [Closed] (CURATOR-603) Use Awaitility to instead of Thread sleep method.

[ https://issues.apache.org/jira/browse/CURATOR-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-603. - Fix Version/s: (was: awaiting-response) Resolution: Won't Fix No response. > Use Awaitility

[jira] [Closed] (CURATOR-653) Double leader for LeaderLatch

[ https://issues.apache.org/jira/browse/CURATOR-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-653. - Resolution: Fixed master via 9b3a145372d9a8bc9a71adb630a1ad9b71fd2889 > Double leader for LeaderLatch

[jira] [Commented] (CURATOR-654) DistributedBarrier watcher leak

[ https://issues.apache.org/jira/browse/CURATOR-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614844#comment-17614844 ] Zili Chen commented on CURATOR-654: --- Thank you [~sscott]! I may review this patch in this week. Sorry

[jira] [Commented] (CURATOR-654) DistributedBarrier watcher leak

[ https://issues.apache.org/jira/browse/CURATOR-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612854#comment-17612854 ] Zili Chen commented on CURATOR-654: --- Hi [~sscott]! Thanks for your reporting. You can directly send a

[jira] [Created] (CURATOR-653) Double leader for LeaderLatch

Zili Chen created CURATOR-653: - Summary: Double leader for LeaderLatch Key: CURATOR-653 URL: https://issues.apache.org/jira/browse/CURATOR-653 Project: Apache Curator Issue Type: Task

[jira] [Closed] (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:all-tabpanel ] Zili Chen closed CURATOR-645. - Fix Version/s: 5.4.0 Assignee: Zili Chen Resolution: Fixed master via

[jira] [Closed] (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 closed CURATOR-644. - Fix Version/s: 5.4.0 Assignee: Zili Chen (was: Jordan Zimmerman) Resolution: Fixed

[jira] [Closed] (CURATOR-473) update the comment of AdvancedTracerDriver.java

[ https://issues.apache.org/jira/browse/CURATOR-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-473. - Resolution: Won't Do Inactive. > update the comment of AdvancedTracerDriver.java >

[jira] [Closed] (CURATOR-445) Curator failed to detect ZooKeeper 3.5.x under OSGi

[ https://issues.apache.org/jira/browse/CURATOR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-445. - Resolution: Won't Fix No progress. > Curator failed to detect ZooKeeper 3.5.x under OSGi >

[jira] [Assigned] (CURATOR-587) Use ZooKeeper 3.7+ ZooKeeperServerEmbedded in order to start TestingServer

[ https://issues.apache.org/jira/browse/CURATOR-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-587: - Assignee: Zili Chen (was: Enrico Olivelli) > Use ZooKeeper 3.7+ ZooKeeperServerEmbedded in

[jira] [Commented] (CURATOR-587) Use ZooKeeper 3.7+ ZooKeeperServerEmbedded in order to start TestingServer

[ https://issues.apache.org/jira/browse/CURATOR-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597680#comment-17597680 ] Zili Chen commented on CURATOR-587: --- OK. I made a draft: https://github.com/apache/curator/pull/434

[jira] [Commented] (CURATOR-587) Use ZooKeeper 3.7+ ZooKeeperServerEmbedded in order to start TestingServer

[ https://issues.apache.org/jira/browse/CURATOR-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597553#comment-17597553 ] Zili Chen commented on CURATOR-587: --- > That embedded ZooKeeper Which one is referred here? The one of

[jira] [Closed] (CURATOR-649) Background exception was not retry-able or retry gave up

[ https://issues.apache.org/jira/browse/CURATOR-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-649. - Fix Version/s: 5.4.0 Assignee: Zili Chen Resolution: Fixed master via

[jira] [Commented] (CURATOR-538) Background exception was not retry-able or retry gave up

[ https://issues.apache.org/jira/browse/CURATOR-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597547#comment-17597547 ] Zili Chen commented on CURATOR-538: --- master via b66240c80e8f289b701e1febfd2f7a3f6aac > Background

[jira] [Closed] (CURATOR-597) Background exception was not retry-able or retry gave up

[ https://issues.apache.org/jira/browse/CURATOR-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-597. - Fix Version/s: 5.4.0 Assignee: Zili Chen Resolution: Fixed master via

[jira] [Closed] (CURATOR-648) CuratorFramework#blockUntilConnected does now wait forever if waitTime <= 0

[ https://issues.apache.org/jira/browse/CURATOR-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-648. - > CuratorFramework#blockUntilConnected does now wait forever if waitTime <= 0 >

[jira] [Resolved] (CURATOR-648) CuratorFramework#blockUntilConnected does now wait forever if waitTime <= 0

[ https://issues.apache.org/jira/browse/CURATOR-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-648. --- Fix Version/s: 5.4.0 Resolution: Fixed master via 917a98ff79954dba0180745627c30c73d885b64c

[jira] [Updated] (CURATOR-648) CuratorFramework#blockUntilConnected does now wait forever if waitTime <= 0

[ https://issues.apache.org/jira/browse/CURATOR-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-648: -- Component/s: Documentation > CuratorFramework#blockUntilConnected does now wait forever if waitTime

[jira] [Assigned] (CURATOR-648) CuratorFramework#blockUntilConnected does now wait forever if waitTime <= 0

[ https://issues.apache.org/jira/browse/CURATOR-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen reassigned CURATOR-648: - Assignee: Zili Chen (was: Jordan Zimmerman) > CuratorFramework#blockUntilConnected does now

[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-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=17568072#comment-17568072 ] Zili Chen commented on CURATOR-640: --- [~dwhitejazz] the issue is fixed. The test is unstable due to JDK

[jira] [Closed] (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 closed CURATOR-524. - Fix Version/s: 5.4.0 Resolution: Fixed master via d4aa4424a2b2e3f3c640937d8d539e8c76e2564a >

[jira] [Closed] (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 closed CURATOR-638. - > Curator disconnect from zookeeper when IPs change > - > >

[jira] [Resolved] (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 resolved CURATOR-638. --- Assignee: Zili Chen Resolution: Fixed master via 46e1536d3309adcfc10c072d84d46d6ab24eb4fc >

[jira] [Closed] (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 closed CURATOR-578. - Resolution: Fixed > EnsembleTracker replace hostname connectString with wrong ip from zk config >

[jira] [Closed] (CURATOR-387) API to validate file path in zookeeper

[ https://issues.apache.org/jira/browse/CURATOR-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-387. - Assignee: Zili Chen Resolution: Information Provided I think {{PathUtils#validatePath}} is exact

[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-371) Reduce logging level for fallback being used instead of features not available in stable ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-371. --- Resolution: Won't Fix Curator 5.x doesn't support ZK 3.4 and thus the issue should vanish. Also,

[jira] [Closed] (CURATOR-371) Reduce logging level for fallback being used instead of features not available in stable ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-371. - > Reduce logging level for fallback being used instead of features not > available in stable ZooKeeper >

[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] [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] [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] [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] [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] [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] [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] [Resolved] (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 resolved CURATOR-233. --- Resolution: Duplicate > Bug in double barrier > - > > Key:

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

[jira] [Updated] (CURATOR-596) Upgrade ZooKeeper to 3.7.1

[ https://issues.apache.org/jira/browse/CURATOR-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-596: -- Summary: Upgrade ZooKeeper to 3.7.1 (was: Upgrade ZooKeeper to 3.7.0) > Upgrade ZooKeeper to 3.7.1 >

[jira] [Resolved] (CURATOR-596) Upgrade ZooKeeper to 3.7.1

[ https://issues.apache.org/jira/browse/CURATOR-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-596. --- Resolution: Fixed master via 8fb978d0ff4569c80dae19514e8605eca6e80cfc > Upgrade ZooKeeper to 3.7.1

[jira] [Updated] (CURATOR-596) Upgrade ZooKeeper to 3.7.0

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

[jira] [Closed] (CURATOR-219) Avoid use of Throwable

[ https://issues.apache.org/jira/browse/CURATOR-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen closed CURATOR-219. - Fix Version/s: (was: awaiting-response) Resolution: Won't Fix See comments on the pull

[jira] [Resolved] (CURATOR-458) Fix Schema constructor validation logic

[ https://issues.apache.org/jira/browse/CURATOR-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen resolved CURATOR-458. --- Fix Version/s: 5.4.0 Resolution: Fixed master via c1b6d86a4a7503b2a6dbc825a951a6aabcbb71b1

[jira] [Updated] (CURATOR-458) Fix Schema constructor validation logic

[ https://issues.apache.org/jira/browse/CURATOR-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zili Chen updated CURATOR-458: -- Summary: Fix Schema constructor validation logic (was: Fix a bug spotted by error-prone compiler) >

[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=17566571#comment-17566571 ] Zili Chen commented on CURATOR-504: --- Also I add several debug log points so that if the issue remains,

[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=17566433#comment-17566433 ] Zili Chen commented on CURATOR-504: --- I think I mix the original logic and patch I made. If we reset on

[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] [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] [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=17566108#comment-17566108 ] Zili Chen commented on CURATOR-644: --- [~rikimberley] I push a patch here:

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

<    1   2   3   >