[jira] [Created] (CURATOR-568) New option allowing CuratorFramework skip ZK ensemble tracking

Evaristo created CURATOR-568: Summary: New option allowing CuratorFramework skip ZK ensemble tracking Key: CURATOR-568 URL: https://issues.apache.org/jira/browse/CURATOR-568 Project: Apache Curator

[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=16772813#comment-16772813 ] Evaristo commented on CURATOR-507: -- Thanks Cameron. I am working with a unit test tryin

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

Evaristo created CURATOR-507: Summary: PERSISTENT NODE ISSUE Key: CURATOR-507 URL: https://issues.apache.org/jira/browse/CURATOR-507 Project: Apache Curator Issue Type: Bug Components:

[jira] [Commented] (CURATOR-506) PersistentNode sometimes deletes more ZNodes that expected when closed

[ https://issues.apache.org/jira/browse/CURATOR-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762861#comment-16762861 ] Evaristo commented on CURATOR-506: -- Thx a lot Jordan. Sorry for the mistake. I was not

[jira] [Updated] (CURATOR-506) PersistentNode sometimes deletes more ZNodes that expected when closed

[ https://issues.apache.org/jira/browse/CURATOR-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-506: - Description: Hi there, I have an application using PersistentNode with CreateMode.EPHEMERAL that is re

[jira] [Updated] (CURATOR-506) PersistentNode sometimes deletes more ZNodes that expected when closed

[ https://issues.apache.org/jira/browse/CURATOR-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-506: - Attachment: PN.patch > PersistentNode sometimes deletes more ZNodes that expected when closed >

[jira] [Created] (CURATOR-506) PersistentNode sometimes deletes more ZNodes that expected when closed

Evaristo created CURATOR-506: Summary: PersistentNode sometimes deletes more ZNodes that expected when closed Key: CURATOR-506 URL: https://issues.apache.org/jira/browse/CURATOR-506 Project: Apache Curato

[jira] [Commented] (CURATOR-109) Threads that are sleeping should get interrupted when closing the client.

[ https://issues.apache.org/jira/browse/CURATOR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020400#comment-14020400 ] Evaristo commented on CURATOR-109: -- I was taking a look to the code. I only saw as prob

[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=14020388#comment-14020388 ] Evaristo commented on CURATOR-106: -- When the ZK goes down you do not get the Exception,

[jira] [Commented] (CURATOR-87) new LeaderLatch "jitters" after network outage

[ https://issues.apache.org/jira/browse/CURATOR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007745#comment-14007745 ] Evaristo commented on CURATOR-87: - Hi there, In my opinion this test is not following the

[jira] [Commented] (CURATOR-90) Reduce the verbosity of connection error log messages

[ https://issues.apache.org/jira/browse/CURATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994325#comment-13994325 ] Evaristo commented on CURATOR-90: - Added property to customize the behaviour https://gith

[jira] [Commented] (CURATOR-90) Reduce the verbosity of connection error log messages

[ https://issues.apache.org/jira/browse/CURATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994858#comment-13994858 ] Evaristo commented on CURATOR-90: - Changed default behaviour. Check pull request > Reduce

[jira] [Commented] (CURATOR-90) Reduce the verbosity of connection error log messages

[ https://issues.apache.org/jira/browse/CURATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988318#comment-13988318 ] Evaristo commented on CURATOR-90: - I made a pull request, but I am not sure if I did it OK

[jira] [Updated] (CURATOR-90) Reduce the verbosity of connection error log messages

[ https://issues.apache.org/jira/browse/CURATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-90: Attachment: curator-90-evaristo.patch I attach a potential patch, It prints the first ocurrence of Connect

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889296#comment-13889296 ] Evaristo commented on CURATOR-72: - The code is basically redundant with checkBackgroundRet

[jira] [Updated] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-72: Attachment: curator-72.patch Hi there, I think I got it. I attach a patch. Please take a look and provide

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888240#comment-13888240 ] Evaristo commented on CURATOR-72: - Hi there, TestListenerWithLeaderSelectorBis shows a sn

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874656#comment-13874656 ] Evaristo commented on CURATOR-72: - Hi there: I have been comparing code in CURATOR-72 (cu

[jira] [Updated] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-72: Attachment: TestListenerWithLeaderSelectorBis.java Previous test work fine now, but now fails a different t

[jira] [Updated] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-72: Attachment: TestListenerWithLeaderSelector.java Finally I have a test that shows the problem (TestListener

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867791#comment-13867791 ] Evaristo commented on CURATOR-72: - Hi there, I am trying to produce a test that shows the

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865344#comment-13865344 ] Evaristo commented on CURATOR-72: - I have run the regression of my app, and I think there

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828573#comment-13828573 ] Evaristo commented on CURATOR-72: - Were you able to check the last test I provided? Anyyw

[jira] [Updated] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-72: Attachment: TestListenerSequence.java I attach a test that show the LOST event is not fired. > Background

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823031#comment-13823031 ] Evaristo commented on CURATOR-72: - You can see sequences like CONNECTED , LOST , SUSPENDED

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820408#comment-13820408 ] Evaristo commented on CURATOR-72: - The problem is not the initial LOST. What is suspicious

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819378#comment-13819378 ] Evaristo commented on CURATOR-72: - Not sure if the comments arrive to the list > Backgrou

[jira] [Updated] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-72: Attachment: TestListener.java I guess there is something wrong with listeners... I attach a test (TestList

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818464#comment-13818464 ] Evaristo commented on CURATOR-72: - You are right. Thanks again for the great support > Ba

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818455#comment-13818455 ] Evaristo commented on CURATOR-72: - It is just the test that you attach to the JIRA and tha

[jira] [Updated] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evaristo updated CURATOR-72: Attachment: TestListenerConnectedAtStart.java > Background operations don't wait for connection timeout > -

[jira] [Commented] (CURATOR-53) PersistentEphemeralNode does not work when ZK server are not available when the node is started

[ https://issues.apache.org/jira/browse/CURATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818401#comment-13818401 ] Evaristo commented on CURATOR-53: - Thanks for the fix > PersistentEphemeralNode does not

[jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout

[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818400#comment-13818400 ] Evaristo commented on CURATOR-72: - I have seen that you have included in the repo a test d