[jira] [Commented] (CURATOR-540) BUILD_INITIAL_CACHE mode will post history child on start

[ https://issues.apache.org/jira/browse/CURATOR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932914#comment-16932914 ] Cameron McKenzie commented on CURATOR-540: -- [~honglun], is what's suggested abo

[jira] [Commented] (CURATOR-540) BUILD_INITIAL_CACHE mode will post history child on start

[ https://issues.apache.org/jira/browse/CURATOR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931916#comment-16931916 ] Cameron McKenzie commented on CURATOR-540: -- I think that you could probably put

[jira] [Commented] (CURATOR-540) BUILD_INITIAL_CACHE mode will post history child on start

[ https://issues.apache.org/jira/browse/CURATOR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931882#comment-16931882 ] Cameron McKenzie commented on CURATOR-540: -- Maybe I'm missing something, but I

[jira] [Commented] (CURATOR-540) BUILD_INITIAL_CACHE mode will post history child on start

[ https://issues.apache.org/jira/browse/CURATOR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931822#comment-16931822 ] Cameron McKenzie commented on CURATOR-540: -- In the 2.7 release it seems that th

[jira] [Commented] (CURATOR-540) BUILD_INITIAL_CACHE mode will post history child on start

[ https://issues.apache.org/jira/browse/CURATOR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930238#comment-16930238 ] Cameron McKenzie commented on CURATOR-540: -- My understanding is that StartMode.

[jira] [Commented] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858231#comment-16858231 ] Cameron McKenzie commented on CURATOR-525: -- I think I agree with you Jordan, I

[jira] [Commented] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858201#comment-16858201 ] Cameron McKenzie commented on CURATOR-525: -- Thanks Jordan, I reproduced the pr

[jira] [Commented] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850492#comment-16850492 ] Cameron McKenzie commented on CURATOR-525: -- True, it is related to the way that

[jira] [Commented] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850306#comment-16850306 ] Cameron McKenzie commented on CURATOR-525: -- I have reproduced the problem with

[jira] [Commented] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850201#comment-16850201 ] Cameron McKenzie commented on CURATOR-525: -- [~randgalt], [~mikhailvaliev] I wil

[jira] [Assigned] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-525: Assignee: Cameron McKenzie > There is a race condition in Curator which might lea

[jira] [Issue Comment Deleted] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-525: - Comment: was deleted (was: [~mikhailvaliev], do you happen to have a self contained test

[jira] [Commented] (CURATOR-525) There is a race condition in Curator which might lead to fake SUSPENDED event and ruin CuratorFrameworkImpl inner state

[ https://issues.apache.org/jira/browse/CURATOR-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850200#comment-16850200 ] Cameron McKenzie commented on CURATOR-525: -- [~mikhailvaliev], do you happen to

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

[ https://issues.apache.org/jira/browse/CURATOR-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806277#comment-16806277 ] Cameron McKenzie commented on CURATOR-514: -- The fix looks fine to me. I'm just

[jira] [Commented] (CURATOR-507) PERSISTENT NODE ISSUE

[ https://issues.apache.org/jira/browse/CURATOR-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773387#comment-16773387 ] Cameron McKenzie commented on CURATOR-507: -- Yep, that's fine. > PERSISTENT NOD

[jira] [Commented] (CURATOR-507) PERSISTENT NODE ISSUE

[ https://issues.apache.org/jira/browse/CURATOR-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772386#comment-16772386 ] Cameron McKenzie commented on CURATOR-507: -- I don't think it's a race condition

[jira] [Closed] (CURATOR-477) Ability to turn off Zk Watches in Curator Framework

[ https://issues.apache.org/jira/browse/CURATOR-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-477. Resolution: Fixed Fix Version/s: 4.1.0 > Ability to turn off Zk Watches in Curator

[jira] [Closed] (CURATOR-487) GzipCompressionProvider produces a lot of finalizable objects

[ https://issues.apache.org/jira/browse/CURATOR-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-487. Resolution: Fixed Fix Version/s: 4.1.0 > GzipCompressionProvider produces a lot of

[jira] [Assigned] (CURATOR-487) GzipCompressionProvider produces a lot of finalizable objects

[ https://issues.apache.org/jira/browse/CURATOR-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-487: Assignee: Cameron McKenzie (was: Jordan Zimmerman) > GzipCompressionProvider pro

[jira] [Updated] (CURATOR-409) TestingQuorumPeerMain does not work with Zookeeper 3.5.3-beta

[ https://issues.apache.org/jira/browse/CURATOR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-409: - Fix Version/s: 2.13.0 > TestingQuorumPeerMain does not work with Zookeeper 3.5.3-beta >

[jira] [Commented] (CURATOR-409) TestingQuorumPeerMain does not work with Zookeeper 3.5.3-beta

[ https://issues.apache.org/jira/browse/CURATOR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702702#comment-16702702 ] Cameron McKenzie commented on CURATOR-409: -- Thanks [~risdenk], I have the 2.x

[jira] [Commented] (CURATOR-409) TestingQuorumPeerMain does not work with Zookeeper 3.5.3-beta

[ https://issues.apache.org/jira/browse/CURATOR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701238#comment-16701238 ] Cameron McKenzie commented on CURATOR-409: -- [~risdenk], actually there is somet

[jira] [Closed] (CURATOR-483) Sequential PersistentNodes with protection don't resync after reconnection

[ https://issues.apache.org/jira/browse/CURATOR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-483. Resolution: Fixed Fix Version/s: 4.1.0 > Sequential PersistentNodes with protection

[jira] [Commented] (CURATOR-409) TestingQuorumPeerMain does not work with Zookeeper 3.5.3-beta

[ https://issues.apache.org/jira/browse/CURATOR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699821#comment-16699821 ] Cameron McKenzie commented on CURATOR-409: -- [~risdenk], sorry having some techn

[jira] [Commented] (CURATOR-409) TestingQuorumPeerMain does not work with Zookeeper 3.5.3-beta

[ https://issues.apache.org/jira/browse/CURATOR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687099#comment-16687099 ] Cameron McKenzie commented on CURATOR-409: -- [~Srdo], [~ajisakaa] Let me know wh

[jira] [Commented] (CURATOR-484) CVE-2014-0085, CVE-2018-8012 known security vulnerabilities

[ https://issues.apache.org/jira/browse/CURATOR-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685744#comment-16685744 ] Cameron McKenzie commented on CURATOR-484: -- Maybe I'm missing something, but lo

[jira] [Commented] (CURATOR-482) zookeeper exists waiting forever

[ https://issues.apache.org/jira/browse/CURATOR-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671074#comment-16671074 ] Cameron McKenzie commented on CURATOR-482: -- [~zhaoziyan], Would you be able to

[jira] [Resolved] (CURATOR-476) PathChildrenCache never gets initialized if a child dies even before a data watch is registered for it

[ https://issues.apache.org/jira/browse/CURATOR-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-476. -- Resolution: Fixed Fix Version/s: 4.1.0 > PathChildrenCache never gets initializ

[jira] [Commented] (CURATOR-472) Test-only code started to be called in prod

[ https://issues.apache.org/jira/browse/CURATOR-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561318#comment-16561318 ] Cameron McKenzie commented on CURATOR-472: -- Thanks, I would have thought that w

[jira] [Commented] (CURATOR-472) Test-only code started to be called in prod

[ https://issues.apache.org/jira/browse/CURATOR-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561315#comment-16561315 ] Cameron McKenzie commented on CURATOR-472: -- Yeah, I believe so, the tests are h

[jira] [Commented] (CURATOR-472) Test-only code started to be called in prod

[ https://issues.apache.org/jira/browse/CURATOR-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561312#comment-16561312 ] Cameron McKenzie commented on CURATOR-472: -- Thanks for the update. So, my initi

[jira] [Commented] (CURATOR-472) Test-only code started to be called in prod

[ https://issues.apache.org/jira/browse/CURATOR-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561307#comment-16561307 ] Cameron McKenzie commented on CURATOR-472: -- This is interesting, as the actual

[jira] [Assigned] (CURATOR-472) Test-only code started to be called in prod

[ https://issues.apache.org/jira/browse/CURATOR-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-472: Assignee: Cameron McKenzie > Test-only code started to be called in prod > --

[jira] [Commented] (CURATOR-469) Give background task a chance to execute in CuratorFramework.close()

[ https://issues.apache.org/jira/browse/CURATOR-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502650#comment-16502650 ] Cameron McKenzie commented on CURATOR-469: -- This sounds like a sensible approac

[jira] [Commented] (CURATOR-468) Closing an active leader selector always logs spurious error

[ https://issues.apache.org/jira/browse/CURATOR-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501269#comment-16501269 ] Cameron McKenzie commented on CURATOR-468: -- Any suggestions for a fix? We can c

[jira] [Closed] (CURATOR-462) InterProcessSemaphoreV2 leaves orphaned lease node if acquiring the semaphore is interrupted at the wrong time

[ https://issues.apache.org/jira/browse/CURATOR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-462. Resolution: Fixed Fix Version/s: 4.0.2 > InterProcessSemaphoreV2 leaves orphaned lea

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440224#comment-16440224 ] Cameron McKenzie commented on CURATOR-460: -- The new tech note looks good. Thanks

[jira] [Resolved] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-460. -- Resolution: Fixed > Timed tolerance for connection suspended leads to simultaneous lead

[jira] [Updated] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-460: - Fix Version/s: 4.0.2 > Timed tolerance for connection suspended leads to simultaneous lea

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433253#comment-16433253 ] Cameron McKenzie commented on CURATOR-460: -- Agreed, [~arrodrigues], not sure whe

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421899#comment-16421899 ] Cameron McKenzie commented on CURATOR-460: -- hey [~arrodrigues], I think creating

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418383#comment-16418383 ] Cameron McKenzie commented on CURATOR-460: -- Thanks [~arrodrigues], do you think

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416601#comment-16416601 ] Cameron McKenzie commented on CURATOR-460: -- I'm referring to timeAtSuspendedEven

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416362#comment-16416362 ] Cameron McKenzie commented on CURATOR-460: -- My reading of the ZK code is that th

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413586#comment-16413586 ] Cameron McKenzie commented on CURATOR-460: -- I'll try and have a look in the next

[jira] [Assigned] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-460: Assignee: Cameron McKenzie > Timed tolerance for connection suspended leads to sim

[jira] [Commented] (CURATOR-460) Timed tolerance for connection suspended leads to simultaneous leaders

[ https://issues.apache.org/jira/browse/CURATOR-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413197#comment-16413197 ] Cameron McKenzie commented on CURATOR-460: -- This seems like a problem with Curat

[jira] [Resolved] (CURATOR-438) Remove calls to MoreExecutors.sameThreadExecutor (deprecated)

[ https://issues.apache.org/jira/browse/CURATOR-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-438. -- Resolution: Fixed Fix Version/s: 4.0.1 > Remove calls to MoreExecutors.sameThrea

[jira] [Resolved] (CURATOR-431) Stat structure not filled when using the idiom create().orSetData()

[ https://issues.apache.org/jira/browse/CURATOR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-431. -- Resolution: Fixed Fix Version/s: 4.0.1 > Stat structure not filled when using th

[jira] [Closed] (CURATOR-431) Stat structure not filled when using the idiom create().orSetData()

[ https://issues.apache.org/jira/browse/CURATOR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-431. > Stat structure not filled when using the idiom create().orSetData() > ---

[jira] [Assigned] (CURATOR-431) Stat structure not filled when using the idiom create().orSetData()

[ https://issues.apache.org/jira/browse/CURATOR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-431: Assignee: Cameron McKenzie > Stat structure not filled when using the idiom create

[jira] [Commented] (CURATOR-411) Make Tests Great Again

[ https://issues.apache.org/jira/browse/CURATOR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028007#comment-16028007 ] Cameron McKenzie commented on CURATOR-411: -- [~iocanel], do you have any recollec

[jira] [Commented] (CURATOR-411) Make Tests Great Again

[ https://issues.apache.org/jira/browse/CURATOR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027982#comment-16027982 ] Cameron McKenzie commented on CURATOR-411: -- Can someone explain the testNewMembe

[jira] [Commented] (CURATOR-411) Make Tests Great Again

[ https://issues.apache.org/jira/browse/CURATOR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027966#comment-16027966 ] Cameron McKenzie commented on CURATOR-411: -- [~randgalt] I'll see what I can trac

[jira] [Commented] (CURATOR-229) No retry on DNS lookup failure

[ https://issues.apache.org/jira/browse/CURATOR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965303#comment-15965303 ] Cameron McKenzie commented on CURATOR-229: -- So you're saying just add an unhandl

[jira] [Commented] (CURATOR-229) No retry on DNS lookup failure

[ https://issues.apache.org/jira/browse/CURATOR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965023#comment-15965023 ] Cameron McKenzie commented on CURATOR-229: -- [~randgalt], [~lvfangmin] Any thoug

[jira] [Commented] (CURATOR-229) No retry on DNS lookup failure

[ https://issues.apache.org/jira/browse/CURATOR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963645#comment-15963645 ] Cameron McKenzie commented on CURATOR-229: -- My concern with modifying the start(

[jira] [Commented] (CURATOR-229) No retry on DNS lookup failure

[ https://issues.apache.org/jira/browse/CURATOR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963556#comment-15963556 ] Cameron McKenzie commented on CURATOR-229: -- I don't believe there's a way of con

[jira] [Commented] (CURATOR-395) Potential null dereference in PersistentNode

[ https://issues.apache.org/jira/browse/CURATOR-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939492#comment-15939492 ] Cameron McKenzie commented on CURATOR-395: -- Do you happen to have a test case th

[jira] [Commented] (CURATOR-390) Create better summary of what Apache Curator is/does

[ https://issues.apache.org/jira/browse/CURATOR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925485#comment-15925485 ] Cameron McKenzie commented on CURATOR-390: -- +1 > Create better summary of what

[jira] [Commented] (CURATOR-390) Create better summary of what Apache Curator is/does

[ https://issues.apache.org/jira/browse/CURATOR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925454#comment-15925454 ] Cameron McKenzie commented on CURATOR-390: -- Looks good to me. A couple of gramma

[jira] [Closed] (CURATOR-361) NamespaceImpl.unfixForNamespace() removes leading slash if namespace is empty

[ https://issues.apache.org/jira/browse/CURATOR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-361. > NamespaceImpl.unfixForNamespace() removes leading slash if namespace is empty > -

[jira] [Resolved] (CURATOR-361) NamespaceImpl.unfixForNamespace() removes leading slash if namespace is empty

[ https://issues.apache.org/jira/browse/CURATOR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-361. -- Resolution: Fixed Fix Version/s: 2.11.2 3.2.2 > NamespaceImpl

[jira] [Commented] (CURATOR-361) NamespaceImpl.unfixForNamespace() removes leading slash if namespace is empty

[ https://issues.apache.org/jira/browse/CURATOR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727486#comment-15727486 ] Cameron McKenzie commented on CURATOR-361: -- Thanks for the PR! > NamespaceImpl.

[jira] [Commented] (CURATOR-360) Allow Zookeeper servers in TestingCluster to listen on network interfaces other than localhost

[ https://issues.apache.org/jira/browse/CURATOR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720993#comment-15720993 ] Cameron McKenzie commented on CURATOR-360: -- Thanks for the PR! > Allow Zookeepe

[jira] [Resolved] (CURATOR-360) Allow Zookeeper servers in TestingCluster to listen on network interfaces other than localhost

[ https://issues.apache.org/jira/browse/CURATOR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-360. -- Resolution: Fixed Fix Version/s: 2.11.2 3.2.2 > Allow Zookeep

[jira] [Closed] (CURATOR-360) Allow Zookeeper servers in TestingCluster to listen on network interfaces other than localhost

[ https://issues.apache.org/jira/browse/CURATOR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-360. > Allow Zookeeper servers in TestingCluster to listen on network interfaces > other than local

[jira] [Commented] (CURATOR-359) Curator can't connect to Read Only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700332#comment-15700332 ] Cameron McKenzie commented on CURATOR-359: -- [~benjamin.jaton] Could you please r

[jira] [Commented] (CURATOR-358) Receiving KeeperException with NoNode when LeaderLatch#getLeader()

[ https://issues.apache.org/jira/browse/CURATOR-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691400#comment-15691400 ] Cameron McKenzie commented on CURATOR-358: -- I wouldn't think it will be any time

[jira] [Closed] (CURATOR-358) Receiving KeeperException with NoNode when LeaderLatch#getLeader()

[ https://issues.apache.org/jira/browse/CURATOR-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-358. > Receiving KeeperException with NoNode when LeaderLatch#getLeader() >

[jira] [Resolved] (CURATOR-358) Receiving KeeperException with NoNode when LeaderLatch#getLeader()

[ https://issues.apache.org/jira/browse/CURATOR-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-358. -- Resolution: Fixed Fix Version/s: 2.11.2 3.2.2 > Receiving Kee

[jira] [Commented] (CURATOR-358) Receiving KeeperException with NoNode when LeaderLatch#getLeader()

[ https://issues.apache.org/jira/browse/CURATOR-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15681926#comment-15681926 ] Cameron McKenzie commented on CURATOR-358: -- There's definitely a race condition

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15648919#comment-15648919 ] Cameron McKenzie commented on CURATOR-280: -- You should just be able to execute t

[jira] [Closed] (CURATOR-356) Allow SASL configuration for TestingServer

[ https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-356. Resolution: Fixed Fix Version/s: 2.11.1 3.2.1 > Allow SASL config

[jira] [Commented] (CURATOR-347) Shared read/write lock acquired by one thread cannot be released by another

[ https://issues.apache.org/jira/browse/CURATOR-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606562#comment-15606562 ] Cameron McKenzie commented on CURATOR-347: -- The InterprocessReadWriteLock works

[jira] [Commented] (CURATOR-356) Allow SASL configuration for TestingServer

[ https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606492#comment-15606492 ] Cameron McKenzie commented on CURATOR-356: -- I think that sounds like a reasonabl

[jira] [Resolved] (CURATOR-354) GzipCompressionProvider leaks native memory

[ https://issues.apache.org/jira/browse/CURATOR-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-354. -- Resolution: Fixed Fix Version/s: 2.11.1 3.2.1 > GzipCompressi

[jira] [Closed] (CURATOR-354) GzipCompressionProvider leaks native memory

[ https://issues.apache.org/jira/browse/CURATOR-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-354. > GzipCompressionProvider leaks native memory > --- > >

[jira] [Commented] (CURATOR-349) Expose extra metrics in TracerDriver

[ https://issues.apache.org/jira/browse/CURATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505541#comment-15505541 ] Cameron McKenzie commented on CURATOR-349: -- I don't really have a strong opinion

[jira] [Resolved] (CURATOR-344) SharedValue watcher should limit work to valid data change events

[ https://issues.apache.org/jira/browse/CURATOR-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-344. -- Resolution: Fixed Fix Version/s: 3.2.1 2.11.0 > SharedValue w

[jira] [Closed] (CURATOR-344) SharedValue watcher should limit work to valid data change events

[ https://issues.apache.org/jira/browse/CURATOR-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-344. > SharedValue watcher should limit work to valid data change events >

[jira] [Closed] (CURATOR-341) create().orSetData() retries indefinitely if node exists

[ https://issues.apache.org/jira/browse/CURATOR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-341. > create().orSetData() retries indefinitely if node exists > --

[jira] [Resolved] (CURATOR-341) create().orSetData() retries indefinitely if node exists

[ https://issues.apache.org/jira/browse/CURATOR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-341. -- Resolution: Fixed Fix Version/s: 3.2.1 > create().orSetData() retries indefinite

[jira] [Commented] (CURATOR-341) create().orSetData() retries indefinitely if node exists

[ https://issues.apache.org/jira/browse/CURATOR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418336#comment-15418336 ] Cameron McKenzie commented on CURATOR-341: -- Thanks for the PR! I probably won't

[jira] [Commented] (CURATOR-341) create().orSetData() retries indefinitely if node exists

[ https://issues.apache.org/jira/browse/CURATOR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414306#comment-15414306 ] Cameron McKenzie commented on CURATOR-341: -- Your assessment looks correct to me.

[jira] [Resolved] (CURATOR-340) Upgrade to ZooKeeper 3.4.8

[ https://issues.apache.org/jira/browse/CURATOR-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-340. -- Resolution: Fixed Fix Version/s: (was: 2.11.0) > Upgrade to ZooKeeper 3.4.8

[jira] [Closed] (CURATOR-340) Upgrade to ZooKeeper 3.4.8

[ https://issues.apache.org/jira/browse/CURATOR-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-340. > Upgrade to ZooKeeper 3.4.8 > -- > > Key: CURATOR-340

[jira] [Assigned] (CURATOR-340) Upgrade to ZooKeeper 3.4.8

[ https://issues.apache.org/jira/browse/CURATOR-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-340: Assignee: Cameron McKenzie > Upgrade to ZooKeeper 3.4.8 >

[jira] [Closed] (CURATOR-337) LeaderSelector logs stack trace with "The leader threw an exception" message erroneously

[ https://issues.apache.org/jira/browse/CURATOR-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-337. > LeaderSelector logs stack trace with "The leader threw an exception" message > erroneously >

[jira] [Resolved] (CURATOR-337) LeaderSelector logs stack trace with "The leader threw an exception" message erroneously

[ https://issues.apache.org/jira/browse/CURATOR-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-337. -- Resolution: Fixed Assignee: Cameron McKenzie Fix Version/s: 2.11.1

[jira] [Commented] (CURATOR-337) LeaderSelector logs stack trace with "The leader threw an exception" message erroneously

[ https://issues.apache.org/jira/browse/CURATOR-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396744#comment-15396744 ] Cameron McKenzie commented on CURATOR-337: -- Thanks for the patch! > LeaderSelec

[jira] [Commented] (CURATOR-337) LeaderSelector logs stack trace with "The leader threw an exception" message erroneously

[ https://issues.apache.org/jira/browse/CURATOR-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396637#comment-15396637 ] Cameron McKenzie commented on CURATOR-337: -- That looks like a reasonable assessm

[jira] [Resolved] (CURATOR-331) Enable to add an UnhandledErrorListener for TreeCache errorHandlers

[ https://issues.apache.org/jira/browse/CURATOR-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-331. -- Resolution: Fixed Fix Version/s: 3.2.0 2.11.0 > Enable to add

[jira] [Resolved] (CURATOR-335) InterProcessSemaphoreV2 can deadlock under network stress

[ https://issues.apache.org/jira/browse/CURATOR-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-335. -- Resolution: Fixed > InterProcessSemaphoreV2 can deadlock under network stress > ---

[jira] [Commented] (CURATOR-331) Enable to add an UnhandledErrorListener for TreeCache errorHandlers

[ https://issues.apache.org/jira/browse/CURATOR-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316081#comment-15316081 ] Cameron McKenzie commented on CURATOR-331: -- [~dragonsinth] do you have any thoug

[jira] [Resolved] (CURATOR-333) TestCleanState can hide test assertions

[ https://issues.apache.org/jira/browse/CURATOR-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-333. -- Resolution: Fixed Fix Version/s: (was: TBD) 3.2.0 > TestC

[jira] [Resolved] (CURATOR-332) Internal watcher tracking for new WatcherRemoveCuratorFramework feature is not correct

[ https://issues.apache.org/jira/browse/CURATOR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-332. -- Resolution: Fixed > Internal watcher tracking for new WatcherRemoveCuratorFramework fea

[jira] [Updated] (CURATOR-327) NamespaceImpl does not report full error message to caller

[ https://issues.apache.org/jira/browse/CURATOR-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-327: - Fix Version/s: (was: 3.1.1) (was: 2.10.1) 3.

[jira] [Updated] (CURATOR-328) PathChildrenCache fails silently if server is unavailable for sufficient time when client starts

[ https://issues.apache.org/jira/browse/CURATOR-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-328: - Fix Version/s: (was: 3.1.1) (was: 2.10.1) 3.

[jira] [Updated] (CURATOR-326) createContainers fails silently if client is not connected

[ https://issues.apache.org/jira/browse/CURATOR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-326: - Fix Version/s: (was: 3.1.1) (was: 2.10.1) 3.

  1   2   3   >