[jira] [Updated] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-355: --- Summary: Curator client fails when connecting to read-only ensemble (was: Curator client

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563014#comment-15563014 ] Benjamin Jaton commented on CURATOR-355: Sounds good, I will check the 3.x release. But I won't

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562989#comment-15562989 ] Jordan Zimmerman commented on CURATOR-355: -- Firstly, the call to

[jira] [Comment Edited] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562989#comment-15562989 ] Jordan Zimmerman edited comment on CURATOR-355 at 10/10/16 6:00 PM:

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562950#comment-15562950 ] Jordan Zimmerman commented on CURATOR-355: -- Is this Curator 3.x? or 2.x? > Curator client fails

[jira] [Comment Edited] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562989#comment-15562989 ] Jordan Zimmerman edited comment on CURATOR-355 at 10/10/16 5:58 PM:

[jira] [Created] (CURATOR-355) Curator client hangs when connecting to read-only ensemble

Benjamin Jaton created CURATOR-355: -- Summary: Curator client hangs when connecting to read-only ensemble Key: CURATOR-355 URL: https://issues.apache.org/jira/browse/CURATOR-355 Project: Apache

[jira] [Updated] (CURATOR-355) Curator client hangs when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-355: --- Attachment: test2.log > Curator client hangs when connecting to read-only ensemble >

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562967#comment-15562967 ] Benjamin Jaton commented on CURATOR-355: I used Curator 2.11.0. > Curator client fails when

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563495#comment-15563495 ] Benjamin Jaton commented on CURATOR-355: Does it need a backport? Just a fix of the existing

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563532#comment-15563532 ] Benjamin Jaton commented on CURATOR-355: Just to clarify, in this case there is still 1 of the ZK

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563375#comment-15563375 ] Jordan Zimmerman commented on CURATOR-355: -- It would be hard to back port to 2.x. > Curator

[GitHub] curator pull request #165: [CURATOR-349] Expose extra metrics in TracerDrive...

Github user Randgalt commented on a diff in the pull request: https://github.com/apache/curator/pull/165#discussion_r82682285 --- Diff: curator-client/src/main/java/org/apache/curator/ConnectionState.java --- @@ -199,13 +202,28 @@ private synchronized void checkTimeouts() throws

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563539#comment-15563539 ] Jordan Zimmerman commented on CURATOR-355: -- Yes - though it's ZooKeeper doing the actual

[jira] [Commented] (CURATOR-272) Spamming of Background operation retry gave up

[ https://issues.apache.org/jira/browse/CURATOR-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15561632#comment-15561632 ] Alex Ivanov commented on CURATOR-272: - [~MCuk], were you able to work around this issue? I'm seeing

[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=15563669#comment-15563669 ] ASF GitHub Bot commented on CURATOR-349: Github user lvfangmin commented on a diff in the pull

[GitHub] curator pull request #165: [CURATOR-349] Expose extra metrics in TracerDrive...

Github user lvfangmin commented on a diff in the pull request: https://github.com/apache/curator/pull/165#discussion_r82691347 --- Diff: curator-client/src/main/java/org/apache/curator/ConnectionState.java --- @@ -199,13 +202,28 @@ private synchronized void checkTimeouts() throws

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563713#comment-15563713 ] Benjamin Jaton commented on CURATOR-355: So when I connect using ZK API directly with

Help with task: Committers Needed!

I would like to help out with the task listed at https://helpwanted.apache.org/task.html?e3cc4f65

[jira] [Resolved] (CURATOR-352) SchemaViolation errors do not contain enough information

[ https://issues.apache.org/jira/browse/CURATOR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman resolved CURATOR-352. -- Resolution: Fixed > SchemaViolation errors do not contain enough information >

Re: Help with task: Committers Needed!

Thanks for offering to help! Please have a look at the open issues here: http://issues.apache.org/jira/browse/CURATOR - if anything appeals to you please give it a try. If you have any questions, please ask them here. -Jordan On Mon, Oct 10, 2016 at 3:30 AM, Thomas Matecki

[GitHub] curator pull request #167: [CURATOR-352] SchemaViolation errors do not conta...

Github user asfgit closed the pull request at: https://github.com/apache/curator/pull/167 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (CURATOR-352) SchemaViolation errors do not contain enough information

[ https://issues.apache.org/jira/browse/CURATOR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15561840#comment-15561840 ] ASF GitHub Bot commented on CURATOR-352: Github user asfgit closed the pull request at: