[jira] [Commented] (ZOOKEEPER-1168) ZooKeeper fails to run with IKVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095163#comment-13095163 ] Hadoop QA commented on ZOOKEEPER-1168: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12492519/ZOOKEEPER-1168.patch against trunk revision 1163106. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/482//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/482//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/482//console This message is automatically generated. > ZooKeeper fails to run with IKVM > > > Key: ZOOKEEPER-1168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 > Project: ZooKeeper > Issue Type: Bug > Components: jmx >Affects Versions: 3.4.0 > Environment: All Architectures. Running with IKVM and OpenJDK instead > of Sun JDK 6. >Reporter: Andrew Finnell >Assignee: Andrew Finnell > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1168.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > OS: Windows 64-bit > JRE: IKVM 7.0.4258 > IKVM 7.0.4258 does not support ManagementFactory.getPlatformMBeanServer(); It > will throw a java.lang.Error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Success: ZOOKEEPER-1168 PreCommit Build #482
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/482/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 138687 lines...] [exec] BUILD SUCCESSFUL [exec] Total time: 0 seconds [exec] [exec] [exec] [exec] [exec] +1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12492519/ZOOKEEPER-1168.patch [exec] against trunk revision 1163106. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/482//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/482//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/482//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] ewCTyER1Q2 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 22 minutes 16 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1168 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Updated] (ZOOKEEPER-1168) ZooKeeper fails to run with IKVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1168: Attachment: ZOOKEEPER-1168.patch Minor update to the patch - we don't allow tabs for indentation in the source. > ZooKeeper fails to run with IKVM > > > Key: ZOOKEEPER-1168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 > Project: ZooKeeper > Issue Type: Bug > Components: jmx >Affects Versions: 3.4.0 > Environment: All Architectures. Running with IKVM and OpenJDK instead > of Sun JDK 6. >Reporter: Andrew Finnell >Assignee: Andrew Finnell > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1168.patch, ZOOKEEPER-1168.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > OS: Windows 64-bit > JRE: IKVM 7.0.4258 > IKVM 7.0.4258 does not support ManagementFactory.getPlatformMBeanServer(); It > will throw a java.lang.Error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1168) ZooKeeper fails to run with IKVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1168: Fix Version/s: (was: 3.5.0) 3.4.0 > ZooKeeper fails to run with IKVM > > > Key: ZOOKEEPER-1168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 > Project: ZooKeeper > Issue Type: Bug > Components: jmx >Affects Versions: 3.4.0 > Environment: All Architectures. Running with IKVM and OpenJDK instead > of Sun JDK 6. >Reporter: Andrew Finnell >Assignee: Andrew Finnell > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-1168.patch, ZOOKEEPER-1168.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > OS: Windows 64-bit > JRE: IKVM 7.0.4258 > IKVM 7.0.4258 does not support ManagementFactory.getPlatformMBeanServer(); It > will throw a java.lang.Error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1168) ZooKeeper fails to run with IKVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095391#comment-13095391 ] Andrew Finnell commented on ZOOKEEPER-1168: --- Won't happen again. > ZooKeeper fails to run with IKVM > > > Key: ZOOKEEPER-1168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 > Project: ZooKeeper > Issue Type: Bug > Components: jmx >Affects Versions: 3.4.0 > Environment: All Architectures. Running with IKVM and OpenJDK instead > of Sun JDK 6. >Reporter: Andrew Finnell >Assignee: Andrew Finnell > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-1168.patch, ZOOKEEPER-1168.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > OS: Windows 64-bit > JRE: IKVM 7.0.4258 > IKVM 7.0.4258 does not support ManagementFactory.getPlatformMBeanServer(); It > will throw a java.lang.Error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1168) ZooKeeper fails to run with IKVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095393#comment-13095393 ] Patrick Hunt commented on ZOOKEEPER-1168: - No worries. Thanks for the patch. > ZooKeeper fails to run with IKVM > > > Key: ZOOKEEPER-1168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 > Project: ZooKeeper > Issue Type: Bug > Components: jmx >Affects Versions: 3.4.0 > Environment: All Architectures. Running with IKVM and OpenJDK instead > of Sun JDK 6. >Reporter: Andrew Finnell >Assignee: Andrew Finnell > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-1168.patch, ZOOKEEPER-1168.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > OS: Windows 64-bit > JRE: IKVM 7.0.4258 > IKVM 7.0.4258 does not support ManagementFactory.getPlatformMBeanServer(); It > will throw a java.lang.Error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Review Request: automating log and snapshot cleaning
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/1043/ --- (Updated 2011-09-01 16:40:46.185217) Review request for zookeeper, Patrick Hunt, Benjamin Reed, and Mahadev Konar. Changes --- updated to 1107.5 patch Summary --- I like to have ZK itself manage the amount of snapshots and logs kept, instead of relying on the PurgeTxnLog utility. This addresses bug ZOOKEEPER-1107. https://issues.apache.org/jira/browse/ZOOKEEPER-1107 Diffs (updated) - ./src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerMain.java 1149082 ./src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerConfig.java 1149082 ./src/java/main/org/apache/zookeeper/server/DatadirCleanupManager.java PRE-CREATION ./conf/zoo_sample.cfg 1149082 ./src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml 1149082 ./src/java/test/org/apache/zookeeper/server/DatadirCleanupManagerTest.java PRE-CREATION Diff: https://reviews.apache.org/r/1043/diff Testing --- test added, passing hudson qa bot. Thanks, Patrick
[jira] [Commented] (ZOOKEEPER-1107) automating log and snapshot cleaning
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095396#comment-13095396 ] jirapos...@reviews.apache.org commented on ZOOKEEPER-1107: -- --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/1043/ --- (Updated 2011-09-01 16:40:46.185217) Review request for zookeeper, Patrick Hunt, Benjamin Reed, and Mahadev Konar. Changes --- updated to 1107.5 patch Summary --- I like to have ZK itself manage the amount of snapshots and logs kept, instead of relying on the PurgeTxnLog utility. This addresses bug ZOOKEEPER-1107. https://issues.apache.org/jira/browse/ZOOKEEPER-1107 Diffs (updated) - ./src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerMain.java 1149082 ./src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerConfig.java 1149082 ./src/java/main/org/apache/zookeeper/server/DatadirCleanupManager.java PRE-CREATION ./conf/zoo_sample.cfg 1149082 ./src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml 1149082 ./src/java/test/org/apache/zookeeper/server/DatadirCleanupManagerTest.java PRE-CREATION Diff: https://reviews.apache.org/r/1043/diff Testing --- test added, passing hudson qa bot. Thanks, Patrick > automating log and snapshot cleaning > > > Key: ZOOKEEPER-1107 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1107 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.3.3 >Reporter: Jun Rao >Assignee: Laxman > Attachments: ZOOKEEPER-1107.1.patch, ZOOKEEPER-1107.2.patch, > ZOOKEEPER-1107.3.patch, ZOOKEEPER-1107.4.patch, ZOOKEEPER-1107.5.patch, > ZOOKEEPER-1107.5.patch, ZOOKEEPER-1107.patch > > > I like to have ZK itself manage the amount of snapshots and logs kept, > instead of relying on the PurgeTxnLog utility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BOOKKEEPER-60) confusion between multiple "consume" methods
[ https://issues.apache.org/jira/browse/BOOKKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095404#comment-13095404 ] Matthieu Morel commented on BOOKKEEPER-60: -- I don't see any 4.0.0 scheduled version. It would probably be worth creating it and specifying it as the fix version for this issue (and others like it). > confusion between multiple "consume" methods > > > Key: BOOKKEEPER-60 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-60 > Project: Bookkeeper > Issue Type: Improvement > Components: hedwig-client >Reporter: Matthieu Morel >Priority: Minor > > There are currently 2 methods named "consume" in the client API: > - in org.apache.hedwig.client.api.MessageHandler : delegates the processing > of a message by a message handler > - in org.apache.hedwig.client.api.Subscriber : notifies the server that > messages have been processed till a given sequence id. This is some kind of > acknowledgement. > I don't think these 2 fundamental methods should be named the same: they have > different purposes and it is confusing. > Couldn't we rename Subscriber.consume into Subscriber.acknowledge, or > something similar? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Success: ZOOKEEPER-1168 PreCommit Build #483
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/483/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 134801 lines...] [exec] BUILD SUCCESSFUL [exec] Total time: 0 seconds [exec] [exec] [exec] [exec] [exec] +1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12492622/ZOOKEEPER-1168.patch [exec] against trunk revision 1163106. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/483//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/483//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/483//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 8H6vPlxia9 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 22 minutes 40 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1168 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-1168) ZooKeeper fails to run with IKVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095414#comment-13095414 ] Hadoop QA commented on ZOOKEEPER-1168: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12492622/ZOOKEEPER-1168.patch against trunk revision 1163106. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/483//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/483//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/483//console This message is automatically generated. > ZooKeeper fails to run with IKVM > > > Key: ZOOKEEPER-1168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 > Project: ZooKeeper > Issue Type: Bug > Components: jmx >Affects Versions: 3.4.0 > Environment: All Architectures. Running with IKVM and OpenJDK instead > of Sun JDK 6. >Reporter: Andrew Finnell >Assignee: Andrew Finnell > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-1168.patch, ZOOKEEPER-1168.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > OS: Windows 64-bit > JRE: IKVM 7.0.4258 > IKVM 7.0.4258 does not support ManagementFactory.getPlatformMBeanServer(); It > will throw a java.lang.Error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1107) automating log and snapshot cleaning
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095421#comment-13095421 ] Hadoop QA commented on ZOOKEEPER-1107: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12490409/ZOOKEEPER-1107.5.patch against trunk revision 1163106. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/484//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/484//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/484//console This message is automatically generated. > automating log and snapshot cleaning > > > Key: ZOOKEEPER-1107 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1107 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.3.3 >Reporter: Jun Rao >Assignee: Laxman > Attachments: ZOOKEEPER-1107.1.patch, ZOOKEEPER-1107.2.patch, > ZOOKEEPER-1107.3.patch, ZOOKEEPER-1107.4.patch, ZOOKEEPER-1107.5.patch, > ZOOKEEPER-1107.5.patch, ZOOKEEPER-1107.patch > > > I like to have ZK itself manage the amount of snapshots and logs kept, > instead of relying on the PurgeTxnLog utility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Success: ZOOKEEPER-1107 PreCommit Build #484
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1107 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/484/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 139539 lines...] [exec] BUILD SUCCESSFUL [exec] Total time: 0 seconds [exec] [exec] [exec] [exec] [exec] +1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12490409/ZOOKEEPER-1107.5.patch [exec] against trunk revision 1163106. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/484//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/484//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/484//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] hC8oBaQukG logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 23 minutes 6 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1107 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
Success: ZOOKEEPER-1168 PreCommit Build #485
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/485/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 140667 lines...] [exec] BUILD SUCCESSFUL [exec] Total time: 0 seconds [exec] [exec] [exec] [exec] [exec] +1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12492622/ZOOKEEPER-1168.patch [exec] against trunk revision 1163106. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/485//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/485//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/485//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] PZYPc77Kjt logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 22 minutes 49 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1168 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-1168) ZooKeeper fails to run with IKVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095427#comment-13095427 ] Hadoop QA commented on ZOOKEEPER-1168: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12492622/ZOOKEEPER-1168.patch against trunk revision 1163106. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/485//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/485//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/485//console This message is automatically generated. > ZooKeeper fails to run with IKVM > > > Key: ZOOKEEPER-1168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1168 > Project: ZooKeeper > Issue Type: Bug > Components: jmx >Affects Versions: 3.4.0 > Environment: All Architectures. Running with IKVM and OpenJDK instead > of Sun JDK 6. >Reporter: Andrew Finnell >Assignee: Andrew Finnell > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-1168.patch, ZOOKEEPER-1168.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > OS: Windows 64-bit > JRE: IKVM 7.0.4258 > IKVM 7.0.4258 does not support ManagementFactory.getPlatformMBeanServer(); It > will throw a java.lang.Error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-851) ZK lets any node to become an observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095436#comment-13095436 ] Vishal Kathuria commented on ZOOKEEPER-851: --- Vishal - I am actually using this behavior as a feature to add observers on demand without having to restart the core ensemble. It is slightly different from the scenario you tried. In my scenario, the 4th node thinks it is an observer (instead of it being a participant). Could you please make sure that the unknown observer scenario works fine with your patch? From what I could tell from reviewing the patch, even an unknown observer will get an INVALID_PEER message. Thanks! Vishal (FB) > ZK lets any node to become an observer > -- > > Key: ZOOKEEPER-851 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-851 > Project: ZooKeeper > Issue Type: Bug > Components: quorum, server >Affects Versions: 3.3.1 >Reporter: Vishal Kher >Assignee: Laxman >Priority: Critical > Fix For: 3.4.0, 3.5.0 > > Attachments: ZOOKEEPER-851.patch > > > I had a 3 node cluster running. The zoo.cfg on each contained 3 entries as > show below: > tickTime=2000 > dataDir=/var/zookeeper > clientPort=2181 > initLimit=5 > syncLimit=2 > server.0=10.150.27.61:2888:3888 > server.1=10.150.27.62:2888:3888 > server.2=10.150.27.63:2888:3888 > I wanted to add another node to the cluster. In fourth node's zoo.cfg, I > created another entry for that node and started zk server. The zoo.cfg on the > first 3 nodes was left unchanged. The fourth node was able to join the > cluster even though the 3 nodes had no idea about the fourth node. > zoo.cfg on fourth node: > tickTime=2000 > dataDir=/var/zookeeper > clientPort=2181 > initLimit=5 > syncLimit=2 > server.0=10.150.27.61:2888:3888 > server.1=10.150.27.62:2888:3888 > server.2=10.150.27.63:2888:3888 > server.3=10.17.117.71:2888:3888 > It looks like 10.17.117.71 is becoming an observer in this case. I was > expecting that the leader will reject 10.17.117.71. > # telnet 10.17.117.71 2181 > Trying 10.17.117.71... > Connected to 10.17.117.71. > Escape character is '^]'. > stat > Zookeeper version: 3.3.0--1, built on 04/02/2010 22:40 GMT > Clients: > /10.17.117.71:37297[1](queued=0,recved=1,sent=0) > Latency min/avg/max: 0/0/0 > Received: 3 > Sent: 2 > Outstanding: 0 > Zxid: 0x20065 > Mode: follower > Node count: 288 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1167) C api lacks syncronous version of sync() call.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095488#comment-13095488 ] Benjamin Reed commented on ZOOKEEPER-1167: -- it wasn't an oversight. there is no reason for a synchronous version. because of the ordering guarantees, if you issue an asynchronous sync, the next call, whether synchronous or asynchronous will see the updated state. > C api lacks syncronous version of sync() call. > -- > > Key: ZOOKEEPER-1167 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1167 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.3.3 >Reporter: Nicholas Harteau > > Reading through the source, the C API implements zoo_async() which is the > zookeeper sync() method implemented in the multithreaded/asynchronous C API. > It doesn't implement anything equivalent in the non-multithreaded API. > I'm not sure if this was oversight or intentional, but it means that the > non-multithreaded API can't guarantee consistent client views on critical > reads. > The zkperl bindings depend on the synchronous, non-multithreaded API so also > can't call sync() currently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-851) ZK lets any node to become an observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095502#comment-13095502 ] Alexander Shraer commented on ZOOKEEPER-851: Hi Vishal, I'm also relying on this feature in the implementation of ZK-107 - this way the new servers are able to join and transfer state before they are added to the cluster, which reduces the time to reconfigure. They become "non-voting followers" (actually, currently they can vote which is fixed in ZK-1113, a sub-bug of ZK-107). This feature also allows removed servers to continue serving clients until the clients switch to new cluster members. Thanks, Alex > ZK lets any node to become an observer > -- > > Key: ZOOKEEPER-851 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-851 > Project: ZooKeeper > Issue Type: Bug > Components: quorum, server >Affects Versions: 3.3.1 >Reporter: Vishal Kher >Assignee: Laxman >Priority: Critical > Fix For: 3.4.0, 3.5.0 > > Attachments: ZOOKEEPER-851.patch > > > I had a 3 node cluster running. The zoo.cfg on each contained 3 entries as > show below: > tickTime=2000 > dataDir=/var/zookeeper > clientPort=2181 > initLimit=5 > syncLimit=2 > server.0=10.150.27.61:2888:3888 > server.1=10.150.27.62:2888:3888 > server.2=10.150.27.63:2888:3888 > I wanted to add another node to the cluster. In fourth node's zoo.cfg, I > created another entry for that node and started zk server. The zoo.cfg on the > first 3 nodes was left unchanged. The fourth node was able to join the > cluster even though the 3 nodes had no idea about the fourth node. > zoo.cfg on fourth node: > tickTime=2000 > dataDir=/var/zookeeper > clientPort=2181 > initLimit=5 > syncLimit=2 > server.0=10.150.27.61:2888:3888 > server.1=10.150.27.62:2888:3888 > server.2=10.150.27.63:2888:3888 > server.3=10.17.117.71:2888:3888 > It looks like 10.17.117.71 is becoming an observer in this case. I was > expecting that the leader will reject 10.17.117.71. > # telnet 10.17.117.71 2181 > Trying 10.17.117.71... > Connected to 10.17.117.71. > Escape character is '^]'. > stat > Zookeeper version: 3.3.0--1, built on 04/02/2010 22:40 GMT > Clients: > /10.17.117.71:37297[1](queued=0,recved=1,sent=0) > Latency min/avg/max: 0/0/0 > Received: 3 > Sent: 2 > Outstanding: 0 > Zxid: 0x20065 > Mode: follower > Node count: 288 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-981) Hang in zookeeper_close() in the multi-threaded C client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095525#comment-13095525
]
Benjamin Reed commented on ZOOKEEPER-981:
-
do you think we could incorporate the test in the tar file into the patch? it
should easily convert to a cppunit test.
> Hang in zookeeper_close() in the multi-threaded C client
>
>
> Key: ZOOKEEPER-981
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-981
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
>Affects Versions: 3.3.2
> Environment: Debian Squeeze, Linux 2.6.32-5, x86_64
>Reporter: Jeremy Stribling
>Assignee: Jeremy Stribling
>Priority: Critical
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-981-v1.patch, ZOOKEEPER-981.tar.gz,
> zookeeper-981.patch
>
>
> I saw a hang once when my C++ application called the zookeeper_close() method
> of the multi-threaded Zookeeper client library. The stack trace of the hung
> thread was the following:
> {quote}
> Thread 8 (Thread 5644):
> #0 0x7f5d7bb5bbe4 in __lll_lock_wait () from /lib/libpthread.so.0
> #1 0x7f5d7bb59ad0 in pthread_cond_broadcast@@GLIBC_2.3.2 () from
> /lib/libpthread.so.0
> #2 0x7f5d793628f6 in unlock_completion_list (l=0x32b4d68) at
> .../zookeeper/src/c/src/mt_adaptor.c:66
> #3 0x7f5d79354d4b in free_completions (zh=0x32b4c80, callCompletion=1,
> reason=-116) at .../zookeeper/src/c/src/zookeeper.c:1069
> #4 0x7f5d79355008 in cleanup_bufs (zh=0x32b4c80, callCompletion=1,
> rc=-116) at .../thirdparty/zookeeper/src/c/src/zookeeper.c:1125
> #5 0x7f5d79353200 in destroy (zh=0x32b4c80) at
> .../thirdparty/zookeeper/src/c/src/zookeeper.c:366
> #6 0x7f5d79358e0e in zookeeper_close (zh=0x32b4c80) at
> .../zookeeper/src/c/src/zookeeper.c:2326
> #7 0x7f5d79356d18 in api_epilog (zh=0x32b4c80, rc=0) at
> .../zookeeper/src/c/src/zookeeper.c:1661
> #8 0x7f5d79362f2f in adaptor_finish (zh=0x32b4c80) at
> .../zookeeper/src/c/src/mt_adaptor.c:205
> #9 0x7f5d79358c8c in zookeeper_close (zh=0x32b4c80) at
> .../zookeeper/src/c/src/zookeeper.c:2297
> ...
> {quote}
> The omitted part of the stack trace is entirely within my application, and
> contains no other calls to/from the Zookeeper client. In particular, I am
> not calling zookeeper_close() from within a completion handler or any of the
> library's threads.
> I haven't been able to reproduce this, and when I encountered this I wasn't
> capturing logging from the client library, so unfortunately I don't have any
> more information at this time. But I will update this JIRA if I see it again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1166) Please add a few svn:ignore properties
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1166: Fix Version/s: (was: 3.3.4) Issue Type: Improvement (was: Bug) > Please add a few svn:ignore properties > -- > > Key: ZOOKEEPER-1166 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1166 > Project: ZooKeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.4.0 >Reporter: Warren Turkal >Assignee: Patrick Hunt >Priority: Minor > Fix For: 3.4.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Please add a couple svn:ignore properties to make dealing with the code > slightly easier. > At the root, please add an svn:ignore property for "build" so that the > default build directory for eclipse is excluded. > At src/java/lib, please add an svn:ignore property for "*.jar" so that jars > acquired by ivy are ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1107) automating log and snapshot cleaning
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1107: Attachment: ZOOKEEPER-1107.6.patch two small updates - one to the conf file and one to the admin guide. > automating log and snapshot cleaning > > > Key: ZOOKEEPER-1107 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1107 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.3.3 >Reporter: Jun Rao >Assignee: Laxman > Attachments: ZOOKEEPER-1107.1.patch, ZOOKEEPER-1107.2.patch, > ZOOKEEPER-1107.3.patch, ZOOKEEPER-1107.4.patch, ZOOKEEPER-1107.5.patch, > ZOOKEEPER-1107.5.patch, ZOOKEEPER-1107.6.patch, ZOOKEEPER-1107.patch > > > I like to have ZK itself manage the amount of snapshots and logs kept, > instead of relying on the PurgeTxnLog utility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1107) automating log and snapshot cleaning
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1107: Fix Version/s: 3.4.0 > automating log and snapshot cleaning > > > Key: ZOOKEEPER-1107 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1107 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.3.3 >Reporter: Jun Rao >Assignee: Laxman > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-1107.1.patch, ZOOKEEPER-1107.2.patch, > ZOOKEEPER-1107.3.patch, ZOOKEEPER-1107.4.patch, ZOOKEEPER-1107.5.patch, > ZOOKEEPER-1107.5.patch, ZOOKEEPER-1107.6.patch, ZOOKEEPER-1107.patch > > > I like to have ZK itself manage the amount of snapshots and logs kept, > instead of relying on the PurgeTxnLog utility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1158) C# client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Hauser updated ZOOKEEPER-1158: --- Attachment: ZOOKEEPER-1158_2.patch > C# client > - > > Key: ZOOKEEPER-1158 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1158 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Eric Hauser >Assignee: Eric Hauser > Attachments: ZOOKEEPER-1158.patch, ZOOKEEPER-1158_2.patch > > > Native C# client for ZooKeeper. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1158) C# client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095711#comment-13095711 ] Eric Hauser commented on ZOOKEEPER-1158: It is a native C# port of the Java client that uses support for C# that was added to jute. In most cases, the API was intentionally keep the same as the Java client in order to make future porting easier. I've added a second patch that adds the code generation necessary to compile to build.xml. > C# client > - > > Key: ZOOKEEPER-1158 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1158 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Eric Hauser >Assignee: Eric Hauser > Attachments: ZOOKEEPER-1158.patch, ZOOKEEPER-1158_2.patch > > > Native C# client for ZooKeeper. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1107) automating log and snapshot cleaning
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095792#comment-13095792
]
Laxman commented on ZOOKEEPER-1107:
---
Thanks very much for your review and update Pat.
{quote}having the period specified in minutes rather than hours{quote}
1) In our case we have gone for this approach as disk is running out of space
after long run say 30 days and even longer. Initially we thought of providing
purge interval in days. But, considering the testability and your point of
finer level of granularity only we have gone for hours.
2) Say, for 3 days interval, user would prefer to configure 72 (hours) rather
4320 (minutes). Just trying to balance usability and granularity.
Please let me know your thoughts on this. If you feel we need more granularity
for some other usecase, surely I can update the patch.
{quote}(my reading of TimerTask indicates that only a single purge operation
would be running at any time, ie they will not run concurrently if I set the
interval to be 1 minute and it takes more than a minute to purge, can you
confirm?){quote}
Yes, verified the behavior of Java Timer. Timer will be running in one single
thread and no two invocations will be running concurrently. Verified the same
through debug points.
> automating log and snapshot cleaning
>
>
> Key: ZOOKEEPER-1107
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1107
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.3.3
>Reporter: Jun Rao
>Assignee: Laxman
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-1107.1.patch, ZOOKEEPER-1107.2.patch,
> ZOOKEEPER-1107.3.patch, ZOOKEEPER-1107.4.patch, ZOOKEEPER-1107.5.patch,
> ZOOKEEPER-1107.5.patch, ZOOKEEPER-1107.6.patch, ZOOKEEPER-1107.patch
>
>
> I like to have ZK itself manage the amount of snapshots and logs kept,
> instead of relying on the PurgeTxnLog utility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-981) Hang in zookeeper_close() in the multi-threaded C client
[
https://issues.apache.org/jira/browse/ZOOKEEPER-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095805#comment-13095805
]
helei commented on ZOOKEEPER-981:
-
I saw the same problem. Maybe ref_counter should be increased before we free zh
> Hang in zookeeper_close() in the multi-threaded C client
>
>
> Key: ZOOKEEPER-981
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-981
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
>Affects Versions: 3.3.2
> Environment: Debian Squeeze, Linux 2.6.32-5, x86_64
>Reporter: Jeremy Stribling
>Assignee: Jeremy Stribling
>Priority: Critical
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-981-v1.patch, ZOOKEEPER-981.tar.gz,
> zookeeper-981.patch
>
>
> I saw a hang once when my C++ application called the zookeeper_close() method
> of the multi-threaded Zookeeper client library. The stack trace of the hung
> thread was the following:
> {quote}
> Thread 8 (Thread 5644):
> #0 0x7f5d7bb5bbe4 in __lll_lock_wait () from /lib/libpthread.so.0
> #1 0x7f5d7bb59ad0 in pthread_cond_broadcast@@GLIBC_2.3.2 () from
> /lib/libpthread.so.0
> #2 0x7f5d793628f6 in unlock_completion_list (l=0x32b4d68) at
> .../zookeeper/src/c/src/mt_adaptor.c:66
> #3 0x7f5d79354d4b in free_completions (zh=0x32b4c80, callCompletion=1,
> reason=-116) at .../zookeeper/src/c/src/zookeeper.c:1069
> #4 0x7f5d79355008 in cleanup_bufs (zh=0x32b4c80, callCompletion=1,
> rc=-116) at .../thirdparty/zookeeper/src/c/src/zookeeper.c:1125
> #5 0x7f5d79353200 in destroy (zh=0x32b4c80) at
> .../thirdparty/zookeeper/src/c/src/zookeeper.c:366
> #6 0x7f5d79358e0e in zookeeper_close (zh=0x32b4c80) at
> .../zookeeper/src/c/src/zookeeper.c:2326
> #7 0x7f5d79356d18 in api_epilog (zh=0x32b4c80, rc=0) at
> .../zookeeper/src/c/src/zookeeper.c:1661
> #8 0x7f5d79362f2f in adaptor_finish (zh=0x32b4c80) at
> .../zookeeper/src/c/src/mt_adaptor.c:205
> #9 0x7f5d79358c8c in zookeeper_close (zh=0x32b4c80) at
> .../zookeeper/src/c/src/zookeeper.c:2297
> ...
> {quote}
> The omitted part of the stack trace is entirely within my application, and
> contains no other calls to/from the Zookeeper client. In particular, I am
> not calling zookeeper_close() from within a completion handler or any of the
> library's threads.
> I haven't been able to reproduce this, and when I encountered this I wasn't
> capturing logging from the client library, so unfortunately I don't have any
> more information at this time. But I will update this JIRA if I see it again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
