[jira] [Updated] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-33: Attachment: CURATOR-33.patch Implementation patch. > Recursive Node Cache > --

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843944#comment-13843944 ] Cameron McKenzie commented on CURATOR-33: - I have supplied a patch + unit tests.

[jira] [Issue Comment Deleted] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-33: Comment: was deleted (was: I have supplied a patch + unit tests.) > Recursive Node Cache >

[jira] [Created] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

Cameron McKenzie created CURATOR-110: Summary: LeaderLatch does not complete if it is started without a connection to ZooKeeper Key: CURATOR-110 URL: https://issues.apache.org/jira/browse/CURATOR-110

[jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019362#comment-14019362 ] Cameron McKenzie commented on CURATOR-110: -- Yes, that's an interesting point act

[jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019377#comment-14019377 ] Cameron McKenzie commented on CURATOR-110: -- Indeed. As for 'wait until connecte

[jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019390#comment-14019390 ] Cameron McKenzie commented on CURATOR-110: -- Sounds reasonable, probably best to

[jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019469#comment-14019469 ] Cameron McKenzie commented on CURATOR-110: -- Ok, I will have a look at modifying

[jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028666#comment-14028666 ] Cameron McKenzie commented on CURATOR-110: -- I've had another chance to look at t

[jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028809#comment-14028809 ] Cameron McKenzie commented on CURATOR-110: -- I've just submitted a pull request f

[jira] [Created] (CURATOR-114) TestingServer should expose restart() method.

Cameron McKenzie created CURATOR-114: Summary: TestingServer should expose restart() method. Key: CURATOR-114 URL: https://issues.apache.org/jira/browse/CURATOR-114 Project: Apache Curator

[jira] [Commented] (CURATOR-110) LeaderLatch does not complete if it is started without a connection to ZooKeeper

[ https://issues.apache.org/jira/browse/CURATOR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034430#comment-14034430 ] Cameron McKenzie commented on CURATOR-110: -- Looks good Jordan. Not sure why (may

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

[ https://issues.apache.org/jira/browse/CURATOR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036784#comment-14036784 ] Cameron McKenzie commented on CURATOR-115: -- Pretty sure this is occurring becaus

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

[ https://issues.apache.org/jira/browse/CURATOR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036926#comment-14036926 ] Cameron McKenzie commented on CURATOR-115: -- Also seems likely that this has not

[jira] [Created] (CURATOR-116) Ordering of delayed distributed queue is inconsistent

Cameron McKenzie created CURATOR-116: Summary: Ordering of delayed distributed queue is inconsistent Key: CURATOR-116 URL: https://issues.apache.org/jira/browse/CURATOR-116 Project: Apache Curator

[jira] [Work started] (CURATOR-116) Ordering of delayed distributed queue is inconsistent

[ https://issues.apache.org/jira/browse/CURATOR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CURATOR-116 started by Cameron McKenzie. > Ordering of delayed distributed queue is inconsistent > - > >

[jira] [Resolved] (CURATOR-116) Ordering of delayed distributed queue is inconsistent

[ https://issues.apache.org/jira/browse/CURATOR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-116. -- Resolution: Fixed Fix Version/s: 2.6.0 > Ordering of delayed distributed queue

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056928#comment-14056928 ] Cameron McKenzie commented on CURATOR-33: - The patch was definitely functional whe

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056941#comment-14056941 ] Cameron McKenzie commented on CURATOR-33: - Nope, I'm happy for it to be moved to a

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056954#comment-14056954 ] Cameron McKenzie commented on CURATOR-33: - Maybe something went missing when apply

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057020#comment-14057020 ] Cameron McKenzie commented on CURATOR-33: - You could clone my github repo https:/

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057057#comment-14057057 ] Cameron McKenzie commented on CURATOR-33: - Up to you, I'm more than happy for you

[jira] [Assigned] (CURATOR-121) PathChildrenCache is throwing an InterruptedException when being closed

[ https://issues.apache.org/jira/browse/CURATOR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-121: Assignee: Cameron McKenzie > PathChildrenCache is throwing an InterruptedException

[jira] [Commented] (CURATOR-121) PathChildrenCache is throwing an InterruptedException when being closed

[ https://issues.apache.org/jira/browse/CURATOR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067404#comment-14067404 ] Cameron McKenzie commented on CURATOR-121: -- When you say 'I intermittently recei

[jira] [Closed] (CURATOR-121) PathChildrenCache is throwing an InterruptedException when being closed

[ https://issues.apache.org/jira/browse/CURATOR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-121. Resolution: Fixed > PathChildrenCache is throwing an InterruptedException when being close

[jira] [Closed] (CURATOR-121) PathChildrenCache is throwing an InterruptedException when being closed

[ https://issues.apache.org/jira/browse/CURATOR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-121. Resolution: Fixed > PathChildrenCache is throwing an InterruptedException when being close

[jira] [Reopened] (CURATOR-121) PathChildrenCache is throwing an InterruptedException when being closed

[ https://issues.apache.org/jira/browse/CURATOR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reopened CURATOR-121: -- > PathChildrenCache is throwing an InterruptedException when being closed > --

[jira] [Updated] (CURATOR-121) PathChildrenCache is throwing an InterruptedException when being closed

[ https://issues.apache.org/jira/browse/CURATOR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-121: - Fix Version/s: 2.6.1 > PathChildrenCache is throwing an InterruptedException when being

[jira] [Closed] (CURATOR-127) Fix trivial warnings

[ https://issues.apache.org/jira/browse/CURATOR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-127. Resolution: Fixed Fix Version/s: 2.6.1 > Fix trivial warnings > ---

[jira] [Assigned] (CURATOR-126) IllegalStateException in performBackgroundOperation during close

[ https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-126: Assignee: Cameron McKenzie > IllegalStateException in performBackgroundOperation d

[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close

[ https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075935#comment-14075935 ] Cameron McKenzie commented on CURATOR-126: -- I've had a bit of a look at this and

[jira] [Commented] (CURATOR-128) There is no namespace-safe way to refer to the root node

[ https://issues.apache.org/jira/browse/CURATOR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077241#comment-14077241 ] Cameron McKenzie commented on CURATOR-128: -- I think that it would be preferable

[jira] [Commented] (CURATOR-128) There is no namespace-safe way to refer to the root node

[ https://issues.apache.org/jira/browse/CURATOR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077398#comment-14077398 ] Cameron McKenzie commented on CURATOR-128: -- This sounds ok to me. It assumes tha

[jira] [Commented] (CURATOR-42) Background guaranteed delete considers NoNode to be a failed delete, and retries it

[ https://issues.apache.org/jira/browse/CURATOR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077447#comment-14077447 ] Cameron McKenzie commented on CURATOR-42: - Just had a look at this, the delete def

[jira] [Closed] (CURATOR-42) Background guaranteed delete considers NoNode to be a failed delete, and retries it

[ https://issues.apache.org/jira/browse/CURATOR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-42. --- Resolution: Fixed Fix Version/s: (was: awaiting-response) 2.7.0

[jira] [Commented] (CURATOR-106) Issuing a guaranteed delete can cause stack overflow if ZK is not reachable

[ https://issues.apache.org/jira/browse/CURATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078715#comment-14078715 ] Cameron McKenzie commented on CURATOR-106: -- I have had a look at this as well, a

[jira] [Comment Edited] (CURATOR-106) Issuing a guaranteed delete can cause stack overflow if ZK is not reachable

[ https://issues.apache.org/jira/browse/CURATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078715#comment-14078715 ] Cameron McKenzie edited comment on CURATOR-106 at 7/30/14 12:50 AM: ---

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

[ https://issues.apache.org/jira/browse/CURATOR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078718#comment-14078718 ] Cameron McKenzie commented on CURATOR-115: -- Can you see if you can reproduce thi

[jira] [Closed] (CURATOR-119) Remove explicit year from Appendix in LICENSE files

[ https://issues.apache.org/jira/browse/CURATOR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-119. Resolution: Fixed Fix Version/s: 2.7.0 > Remove explicit year from Appendix in LICE

[jira] [Commented] (CURATOR-133) NodeCache doesn't properly respect namespaced curators

[ https://issues.apache.org/jira/browse/CURATOR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082014#comment-14082014 ] Cameron McKenzie commented on CURATOR-133: -- Can you provide a test case to repro

[jira] [Assigned] (CURATOR-132) setACL doesn't work with namespaced curator

[ https://issues.apache.org/jira/browse/CURATOR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-132: Assignee: Cameron McKenzie > setACL doesn't work with namespaced curator > ---

[jira] [Commented] (CURATOR-132) setACL doesn't work with namespaced curator

[ https://issues.apache.org/jira/browse/CURATOR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082043#comment-14082043 ] Cameron McKenzie commented on CURATOR-132: -- This appears to happen because setAC

[jira] [Commented] (CURATOR-132) setACL doesn't work with namespaced curator

[ https://issues.apache.org/jira/browse/CURATOR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083777#comment-14083777 ] Cameron McKenzie commented on CURATOR-132: -- Regression all seems to run fine wit

[jira] [Closed] (CURATOR-67) Issue with default JSONInstanceSerializer for discovery service builder

[ https://issues.apache.org/jira/browse/CURATOR-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-67. --- Resolution: Fixed Fix Version/s: (was: awaiting-response) 2.7.0

[jira] [Closed] (CURATOR-71) Error message in StandardLockInternalsDriver for retryable lock acquire error

[ https://issues.apache.org/jira/browse/CURATOR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-71. --- Resolution: Fixed Fix Version/s: 2.7.0 > Error message in StandardLockInternalsDriver

[jira] [Commented] (CURATOR-79) InterProcessMutex doesn't clean up after interrupt

[ https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1400#comment-1400 ] Cameron McKenzie commented on CURATOR-79: - If you run this test twice, won't the s

[jira] [Commented] (CURATOR-79) InterProcessMutex doesn't clean up after interrupt

[ https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088915#comment-14088915 ] Cameron McKenzie commented on CURATOR-79: - I've made some changes to the unit test

[jira] [Commented] (CURATOR-79) InterProcessMutex doesn't clean up after interrupt

[ https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088960#comment-14088960 ] Cameron McKenzie commented on CURATOR-79: - I will certainly upload with a fix. It'

[jira] [Commented] (CURATOR-79) InterProcessMutex doesn't clean up after interrupt

[ https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090347#comment-14090347 ] Cameron McKenzie commented on CURATOR-79: - So, a fix for this is more complicated

[jira] [Closed] (CURATOR-131) Should not modify collection while iterating over it

[ https://issues.apache.org/jira/browse/CURATOR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-131. Resolution: Fixed > Should not modify collection while iterating over it > ---

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093689#comment-14093689 ] Cameron McKenzie commented on CURATOR-134: -- I've had a look into this and can ce

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095109#comment-14095109 ] Cameron McKenzie commented on CURATOR-134: -- Right, misinterpretation of LOST sta

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101930#comment-14101930 ] Cameron McKenzie commented on CURATOR-134: -- I think that I've tracked down what

[jira] [Closed] (CURATOR-139) Add slf4j logging implementation to test scope

[ https://issues.apache.org/jira/browse/CURATOR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-139. Resolution: Fixed Fix Version/s: 2.7.0 > Add slf4j logging implementation to test s

[jira] [Closed] (CURATOR-141) Avoid confusing error logging when PathChildrenCache and curator client are closed.

[ https://issues.apache.org/jira/browse/CURATOR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-141. Resolution: Fixed > Avoid confusing error logging when PathChildrenCache and curator clien

[jira] [Closed] (CURATOR-147) Avoid internal use of deprecated APIs

[ https://issues.apache.org/jira/browse/CURATOR-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-147. Resolution: Fixed > Avoid internal use of deprecated APIs > ---

[jira] [Closed] (CURATOR-149) ChildData's path check prevents the initialization of PathChildrenCache class

[ https://issues.apache.org/jira/browse/CURATOR-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-149. Resolution: Fixed This has been fixed independently as part of CURATOR-136. Commit is 6344

[jira] [Closed] (CURATOR-156) A typo error in "PathCacheExample"

[ https://issues.apache.org/jira/browse/CURATOR-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-156. Resolution: Fixed Fix Version/s: 2.7.0 > A typo error in "PathCacheExample" > --

[jira] [Assigned] (CURATOR-154) PersistentEphemeralNode May Fail to Apply Updated Data

[ https://issues.apache.org/jira/browse/CURATOR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie reassigned CURATOR-154: Assignee: Cameron McKenzie > PersistentEphemeralNode May Fail to Apply Updated Dat

[jira] [Commented] (CURATOR-162) Support Local Sessions

[ https://issues.apache.org/jira/browse/CURATOR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194194#comment-14194194 ] Cameron McKenzie commented on CURATOR-162: -- I had a brief look at this (https:/

[jira] [Closed] (CURATOR-140) Support the initial data for the node in InterProcessReadWriteLock

[ https://issues.apache.org/jira/browse/CURATOR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-140. Resolution: Fixed Fix Version/s: 2.7.1 > Support the initial data for the node in In

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216764#comment-14216764 ] Cameron McKenzie commented on CURATOR-167: -- I can reproduce the problem on a WIn

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216788#comment-14216788 ] Cameron McKenzie commented on CURATOR-167: -- Looking briefly at the code, it woul

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216847#comment-14216847 ] Cameron McKenzie commented on CURATOR-167: -- Yep, good call. Unfortunately this o

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216864#comment-14216864 ] Cameron McKenzie commented on CURATOR-167: -- This definitely reduces the size of

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216925#comment-14216925 ] Cameron McKenzie commented on CURATOR-167: -- [~randgalt] I tried adding all of th

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216937#comment-14216937 ] Cameron McKenzie commented on CURATOR-167: -- [~randgalt] that would explain the Z

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216969#comment-14216969 ] Cameron McKenzie commented on CURATOR-167: -- Yep, had a brief look through the ZK

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217050#comment-14217050 ] Cameron McKenzie commented on CURATOR-167: -- Ok, so if I modify the test slightly

[jira] [Updated] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-167: - Fix Version/s: 3.0.0 > Memory leak in NodeCache > > >

[jira] [Commented] (CURATOR-167) All registered watchers should be cleared on close

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217282#comment-14217282 ] Cameron McKenzie commented on CURATOR-167: -- [~dragonsinth] good point. We should

[jira] [Commented] (CURATOR-167) All registered watchers should be cleared on close

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217297#comment-14217297 ] Cameron McKenzie commented on CURATOR-167: -- Ok. Will sort out a fix > All regis

[jira] [Commented] (CURATOR-161) Support Watcher Removal

[ https://issues.apache.org/jira/browse/CURATOR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225683#comment-14225683 ] Cameron McKenzie commented on CURATOR-161: -- [~randgalt], are you looking at this

[jira] [Commented] (CURATOR-172) Deadlock when performing background operation

[ https://issues.apache.org/jira/browse/CURATOR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247224#comment-14247224 ] Cameron McKenzie commented on CURATOR-172: -- I'm pretty sure I've seen this occur

[jira] [Commented] (CURATOR-172) Deadlock when performing background operation

[ https://issues.apache.org/jira/browse/CURATOR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247398#comment-14247398 ] Cameron McKenzie commented on CURATOR-172: -- I've had a bit of a look through the

[jira] [Commented] (CURATOR-172) Deadlock when performing background operation

[ https://issues.apache.org/jira/browse/CURATOR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249686#comment-14249686 ] Cameron McKenzie commented on CURATOR-172: -- I think that we just ran into the sa

[jira] [Commented] (CURATOR-172) Deadlock when performing background operation

[ https://issues.apache.org/jira/browse/CURATOR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250626#comment-14250626 ] Cameron McKenzie commented on CURATOR-172: -- Had a bit more of a look, and I don'

[jira] [Commented] (CURATOR-179) Sequential path creation of /somepath/N throws exception

[ https://issues.apache.org/jira/browse/CURATOR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267189#comment-14267189 ] Cameron McKenzie commented on CURATOR-179: -- You're correct about where the issue

[jira] [Commented] (CURATOR-179) Sequential path creation of /somepath/N throws exception

[ https://issues.apache.org/jira/browse/CURATOR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268223#comment-14268223 ] Cameron McKenzie commented on CURATOR-179: -- In the path validation code in ZK it

[jira] [Commented] (CURATOR-179) Sequential path creation of /somepath/N throws exception

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

[jira] [Commented] (CURATOR-179) Sequential path creation of /somepath/N throws exception

[ https://issues.apache.org/jira/browse/CURATOR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268778#comment-14268778 ] Cameron McKenzie commented on CURATOR-179: -- I have added a simple test case to t

[jira] [Commented] (CURATOR-179) Sequential path creation of /somepath/N throws exception

[ https://issues.apache.org/jira/browse/CURATOR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268900#comment-14268900 ] Cameron McKenzie commented on CURATOR-179: -- Thanks Scott, Looks good to me. I wo

[jira] [Closed] (CURATOR-179) Sequential path creation of /somepath/N throws exception

[ https://issues.apache.org/jira/browse/CURATOR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-179. Resolution: Fixed Fix Version/s: 2.7.1 > Sequential path creation of /somepath/N thr

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279358#comment-14279358 ] Cameron McKenzie commented on CURATOR-134: -- I think that regardless of the inter

[jira] [Closed] (CURATOR-187) ChildReaper does not respect built in leader election

[ https://issues.apache.org/jira/browse/CURATOR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-187. Resolution: Fixed Fix Version/s: 2.7.2 > ChildReaper does not respect built in leade

[jira] [Assigned] (CURATOR-190) PersistentEphemeralNode.Mode.PROTECTED_EPHEMERAL creates new node on recreate

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

[jira] [Work started] (CURATOR-190) PersistentEphemeralNode.Mode.PROTECTED_EPHEMERAL creates new node on recreate

[ https://issues.apache.org/jira/browse/CURATOR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CURATOR-190 started by Cameron McKenzie. > PersistentEphemeralNode.Mode.PROTECTED_EPHEMERAL creates new node on r

[jira] [Commented] (CURATOR-194) Deadlock in ConnectionState.checkTimeouts

[ https://issues.apache.org/jira/browse/CURATOR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377627#comment-14377627 ] Cameron McKenzie commented on CURATOR-194: -- Possibly a duplicate of CURATOR-172?

[jira] [Closed] (CURATOR-190) PersistentEphemeralNode.Mode.PROTECTED_EPHEMERAL creates new node on recreate

[ https://issues.apache.org/jira/browse/CURATOR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-190. Resolution: Fixed Fix Version/s: 2.7.2 > PersistentEphemeralNode.Mode.PROTECTED_EPHE

[jira] [Closed] (CURATOR-154) PersistentEphemeralNode May Fail to Apply Updated Data

[ https://issues.apache.org/jira/browse/CURATOR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-154. Resolution: Fixed Fix Version/s: 2.8.0 > PersistentEphemeralNode May Fail to Apply U

[jira] [Commented] (CURATOR-190) PersistentEphemeralNode.Mode.PROTECTED_EPHEMERAL creates new node on recreate

[ https://issues.apache.org/jira/browse/CURATOR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516082#comment-14516082 ] Cameron McKenzie commented on CURATOR-190: -- [~randgalt], I can see that testList

[jira] [Commented] (CURATOR-190) PersistentEphemeralNode.Mode.PROTECTED_EPHEMERAL creates new node on recreate

[ https://issues.apache.org/jira/browse/CURATOR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516089#comment-14516089 ] Cameron McKenzie commented on CURATOR-190: -- I have pushed a fix on the CURATOR-1

[jira] [Commented] (CURATOR-164) curator-x-discovery: unregisterService is not guaranteed to remove the service, due to reconnectListener concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516171#comment-14516171 ] Cameron McKenzie commented on CURATOR-164: -- Not sure why the build has suddenly

[jira] [Commented] (CURATOR-164) curator-x-discovery: unregisterService is not guaranteed to remove the service, due to reconnectListener concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516218#comment-14516218 ] Cameron McKenzie commented on CURATOR-164: -- Calling restart() on the TestingServ

[jira] [Created] (CURATOR-210) Unit tests using server.close() are fragile.

Cameron McKenzie created CURATOR-210: Summary: Unit tests using server.close() are fragile. Key: CURATOR-210 URL: https://issues.apache.org/jira/browse/CURATOR-210 Project: Apache Curator

[jira] [Closed] (CURATOR-210) Unit tests using server.close() are fragile.

[ https://issues.apache.org/jira/browse/CURATOR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-210. Resolution: Fixed Fix Version/s: 2.8.0 > Unit tests using server.close() are fragile

[jira] [Closed] (CURATOR-190) PersistentEphemeralNode.Mode.PROTECTED_EPHEMERAL creates new node on recreate

[ https://issues.apache.org/jira/browse/CURATOR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie closed CURATOR-190. Resolution: Fixed Unit tests fixed as part of CURATOR-210 > PersistentEphemeralNode.Mode.P

[jira] [Commented] (CURATOR-167) All registered watchers should be cleared on close

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529908#comment-14529908 ] Cameron McKenzie commented on CURATOR-167: -- I made some changes that minimised t

[jira] [Comment Edited] (CURATOR-167) All registered watchers should be cleared on close

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529908#comment-14529908 ] Cameron McKenzie edited comment on CURATOR-167 at 5/6/15 4:46 AM: -

[jira] [Commented] (CURATOR-224) Locking Not Working with DistributedIdQueue

[ https://issues.apache.org/jira/browse/CURATOR-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592680#comment-14592680 ] Cameron McKenzie commented on CURATOR-224: -- Please create a PR with a fix and un

  1   2   3   >