[jira] [Resolved] (ZOOKEEPER-2336) Jenkins not working due to old SVN
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akihiro Suda resolved ZOOKEEPER-2336.
-
Resolution: Fixed
Closed via INFRA-10919
> Jenkins not working due to old SVN
> --
>
> Key: ZOOKEEPER-2336
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2336
> Project: ZooKeeper
> Issue Type: Test
> Components: build
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
> Attachments: ZOOKEEPER-2336-v1.patch
>
>
> Jenkins seems not working since Build #2976 (Dec 6, 2015) due to SVN.
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2976/console
> {panel}
> [exec] svn: E155036: Please see the 'svn upgrade' command
> [exec] svn: E155036: The working copy at
> '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk'
> [exec] is too old (format 10) to work with client version '1.8.8
> (r1568071)' (expects format 31). You need to upgrade the working copy first.
> [exec]
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-1604 PreCommit Build #3077
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3077/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 125 lines...] [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12726926/ZOOKEEPER-1604.001.patch [exec] against trunk revision 1733348. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3077//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] 17e16d2216ac9f7f34191d1d9dc4903d36f5f099 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 1 Total time: 43 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-1604 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2336) Jenkins not working due to old SVN
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177448#comment-15177448
]
Akihiro Suda commented on ZOOKEEPER-2336:
-
Yes, the server H8 is now working:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3076/
(test failure in this job is unrelated to SVN)
> Jenkins not working due to old SVN
> --
>
> Key: ZOOKEEPER-2336
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2336
> Project: ZooKeeper
> Issue Type: Test
> Components: build
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
> Attachments: ZOOKEEPER-2336-v1.patch
>
>
> Jenkins seems not working since Build #2976 (Dec 6, 2015) due to SVN.
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2976/console
> {panel}
> [exec] svn: E155036: Please see the 'svn upgrade' command
> [exec] svn: E155036: The working copy at
> '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk'
> [exec] is too old (format 10) to work with client version '1.8.8
> (r1568071)' (expects format 31). You need to upgrade the working copy first.
> [exec]
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1604) remove rpm/deb/... packaging
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1604: Assignee: Chris Nauroth (was: Patrick Hunt) > remove rpm/deb/... packaging > > > Key: ZOOKEEPER-1604 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1604 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.3.0 >Reporter: Patrick Hunt >Assignee: Chris Nauroth > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-1604.001.patch > > > Remove rpm/deb/... packaging from our source repo. Now that BigTop is > available and fully supporting ZK it's no longer necessary for us to attempt > to include this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2378) upgrade ivy to recent version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2378: Issue Type: Improvement (was: Bug) Summary: upgrade ivy to recent version (was: Packers) > upgrade ivy to recent version > - > > Key: ZOOKEEPER-2378 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 > Project: ZooKeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.4.8, 3.5.1, 3.6.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2378.patch > > > 2.4.0 is the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2378) Packers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akash Singh updated ZOOKEEPER-2378: --- Description: http://www.expert5th.in/packers-and-movers-pune/ http://www.expert5th.in/packers-and-movers-bangalore/ http://www.expert5th.in/packers-and-movers-hyderabad/ http://www.expert5th.in/packers-and-movers-delhi/ http://www.expert5th.in/packers-and-movers-gurgaon/ http://www.expert5th.in/packers-and-movers-mumbai/ http://www.expert5th.in/packers-and-movers-chennai/ was:2.4.0 is the current version. Issue Type: Bug (was: Improvement) Summary: Packers (was: upgrade ivy to recent version) > Packers > --- > > Key: ZOOKEEPER-2378 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.4.8, 3.5.1, 3.6.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2378.patch > > > http://www.expert5th.in/packers-and-movers-pune/ > http://www.expert5th.in/packers-and-movers-bangalore/ > http://www.expert5th.in/packers-and-movers-hyderabad/ > http://www.expert5th.in/packers-and-movers-delhi/ > http://www.expert5th.in/packers-and-movers-gurgaon/ > http://www.expert5th.in/packers-and-movers-mumbai/ > http://www.expert5th.in/packers-and-movers-chennai/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2373) Licenses section missing from pom file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177423#comment-15177423
]
Hadoop QA commented on ZOOKEEPER-2373:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12791118/ZOOKEEPER-2373.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 appears to introduce 1 new Findbugs (version 2.0.3)
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/3075//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//console
This message is automatically generated.
> Licenses section missing from pom file
> --
>
> Key: ZOOKEEPER-2373
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2373
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Flavio Junqueira
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2373.patch
>
>
> The pom file here:
> https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.8/zookeeper-3.4.8.pom
> should have a section like this:
> {noformat}
>
>
> The Apache Software License, Version 2.0
> http://www.apache.org/licenses/LICENSE-2.0.txt
>
> repo
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2378) upgrade ivy to recent version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177422#comment-15177422 ] Hadoop QA commented on ZOOKEEPER-2378: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12791117/ZOOKEEPER-2378.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +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 appears to introduce 1 new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3076//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3076//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3076//console This message is automatically generated. > upgrade ivy to recent version > - > > Key: ZOOKEEPER-2378 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 > Project: ZooKeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.4.8, 3.5.1, 3.6.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2378.patch > > > 2.4.0 is the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2378 PreCommit Build #3076
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3076/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 377859 lines...] [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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 failed 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/3076//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3076//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3076//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] 3f31ae7c870ac66b141d75ce2256977480ed14a3 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 3 Total time: 12 minutes 38 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Compressed 549.18 KB of artifacts by 35.0% relative to #3049 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2378 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## 1 tests failed. FAILED: org.apache.zookeeper.test.AsyncHammerTest.testHammer Error Message: null Stack Trace: junit.framework.AssertionFailedError at org.apache.zookeeper.test.AsyncHammerTest.testHammer(AsyncHammerTest.java:186) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
Failed: ZOOKEEPER-2373 PreCommit Build #3075
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2373 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 378830 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3075//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3075//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] 12532e55101043c1f6b06a8b9c8d75bafc0fdf33 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 17 minutes 11 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2373 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2317) Non-OSGi compatible version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177411#comment-15177411 ] Patrick Hunt commented on ZOOKEEPER-2317: - Marking this as a blocker for 3.5.2 given you can't deploy to OSGI containers (and we want to enable as many folks as possible) > Non-OSGi compatible version > --- > > Key: ZOOKEEPER-2317 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 > Environment: Karaf OSGi container >Reporter: Markus Tippmann >Priority: Blocker > Fix For: 3.5.2 > > > Bundle cannot be deployed to OSGi container. > Manifest version is not OSGi compatible. > Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2317) Non-OSGi compatible version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2317: Fix Version/s: 3.5.2 > Non-OSGi compatible version > --- > > Key: ZOOKEEPER-2317 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 > Environment: Karaf OSGi container >Reporter: Markus Tippmann > Fix For: 3.5.2 > > > Bundle cannot be deployed to OSGi container. > Manifest version is not OSGi compatible. > Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2317) Non-OSGi compatible version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2317: Priority: Blocker (was: Major) > Non-OSGi compatible version > --- > > Key: ZOOKEEPER-2317 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2317 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 > Environment: Karaf OSGi container >Reporter: Markus Tippmann >Priority: Blocker > Fix For: 3.5.2 > > > Bundle cannot be deployed to OSGi container. > Manifest version is not OSGi compatible. > Instead of using 3.5.1-alpha, manifest needs to contain 3.5.1.alpha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2336) Jenkins not working due to old SVN
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177408#comment-15177408
]
Patrick Hunt commented on ZOOKEEPER-2336:
-
[~rgs] [~suda] are we done with this given INFRA-10919 is closed?
> Jenkins not working due to old SVN
> --
>
> Key: ZOOKEEPER-2336
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2336
> Project: ZooKeeper
> Issue Type: Test
> Components: build
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
> Attachments: ZOOKEEPER-2336-v1.patch
>
>
> Jenkins seems not working since Build #2976 (Dec 6, 2015) due to SVN.
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2976/console
> {panel}
> [exec] svn: E155036: Please see the 'svn upgrade' command
> [exec] svn: E155036: The working copy at
> '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk'
> [exec] is too old (format 10) to work with client version '1.8.8
> (r1568071)' (expects format 31). You need to upgrade the working copy first.
> [exec]
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1162) consistent handling of jute.maxbuffer when attempting to read large zk "directories"
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sunhaitao updated ZOOKEEPER-1162: - Description: Recently we encountered a sitaution where a zk directory got sucessfully populated with 250k elements. When our system attempted to read the znode dir, it failed because the contents of the dir exceeded the default 1mb jute.maxbuffer limit. There were a few odd things 1) It seems odd that we could populate to be very large but could not read the listing 2) The workaround was bumping up jute.maxbuffer on the client side Would it make more sense to have it reject adding new znodes if it exceeds jute.maxbuffer? Alternately, would it make sense to have zk dir listing ignore the jute.maxbuffer setting? was: Recently we encountered a sitaution where a zk directory got sucessfully populated with 250k elements. When our system attempted to read the znode dir, it failed because the contents of the dir exceeded the default 1mb jute.maxbuffer limit. There were a few odd things 1) It seems odd that we could populate to be very large but could not read the listing 2) The workaround was bumping up jute.maxbuffer on the c Would it make more sense to have it reject adding new znodes if it exceeds jute.maxbuffer? Alternately, would it make sense to have zk dir listing ignore the jute.maxbuffer setting? > consistent handling of jute.maxbuffer when attempting to read large zk > "directories" > > > Key: ZOOKEEPER-1162 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1162 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.3.3 >Reporter: Jonathan Hsieh >Priority: Critical > Fix For: 3.5.2, 3.6.0 > > > Recently we encountered a sitaution where a zk directory got sucessfully > populated with 250k elements. When our system attempted to read the znode > dir, it failed because the contents of the dir exceeded the default 1mb > jute.maxbuffer limit. There were a few odd things > 1) It seems odd that we could populate to be very large but could not read > the listing > 2) The workaround was bumping up jute.maxbuffer on the client side > Would it make more sense to have it reject adding new znodes if it exceeds > jute.maxbuffer? > Alternately, would it make sense to have zk dir listing ignore the > jute.maxbuffer setting? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1162) consistent handling of jute.maxbuffer when attempting to read large zk "directories"
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sunhaitao updated ZOOKEEPER-1162: - Description: Recently we encountered a sitaution where a zk directory got sucessfully populated with 250k elements. When our system attempted to read the znode dir, it failed because the contents of the dir exceeded the default 1mb jute.maxbuffer limit. There were a few odd things 1) It seems odd that we could populate to be very large but could not read the listing 2) The workaround was bumping up jute.maxbuffer on the c Would it make more sense to have it reject adding new znodes if it exceeds jute.maxbuffer? Alternately, would it make sense to have zk dir listing ignore the jute.maxbuffer setting? was: Recently we encountered a sitaution where a zk directory got sucessfully populated with 250k elements. When our system attempted to read the znode dir, it failed because the contents of the dir exceeded the default 1mb jute.maxbuffer limit. There were a few odd things 1) It seems odd that we could populate to be very large but could not read the listing 2) The workaround was bumping up jute.maxbuffer on the client side setting. Would it make more sense to have it reject adding new znodes if it exceeds jute.maxbuffer? Alternately, would it make sense to have zk dir listing ignore the jute.maxbuffer setting? > consistent handling of jute.maxbuffer when attempting to read large zk > "directories" > > > Key: ZOOKEEPER-1162 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1162 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.3.3 >Reporter: Jonathan Hsieh >Priority: Critical > Fix For: 3.5.2, 3.6.0 > > > Recently we encountered a sitaution where a zk directory got sucessfully > populated with 250k elements. When our system attempted to read the znode > dir, it failed because the contents of the dir exceeded the default 1mb > jute.maxbuffer limit. There were a few odd things > 1) It seems odd that we could populate to be very large but could not read > the listing > 2) The workaround was bumping up jute.maxbuffer on the c > Would it make more sense to have it reject adding new znodes if it exceeds > jute.maxbuffer? > Alternately, would it make sense to have zk dir listing ignore the > jute.maxbuffer setting? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2372) Add ability to specify user under which zookeeper process should be started using zkServer.sh
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177391#comment-15177391 ] Patrick Hunt commented on ZOOKEEPER-2372: - Why wouldn't the user just make sure to run the script as the proper user? We typically don't deal with this level of detail - we leave it to the package maintainers (such as bigtop). zkServer scripts have historically been more of a convenience. > Add ability to specify user under which zookeeper process should be started > using zkServer.sh > - > > Key: ZOOKEEPER-2372 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2372 > Project: ZooKeeper > Issue Type: Improvement > Components: scripts >Affects Versions: 3.4.8 > Environment: Linux Centos 6 > Java 1.7 >Reporter: Siddhartha >Priority: Minor > > Currently the zkServer.sh script will start zookeeper as the user invoking > the script. > It would be good to add the ability to specify the user (maybe in a $USER > variable in conf/zookeeper-env.sh) under which the zookeeper process should > be run, so that any user invoking the script do not accidentally start it as > their user (esp. as root). > Addition of this feature would make zkServer.sh the only script required to > manage zookeeper process. > Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2378) upgrade ivy to recent version
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2378: Attachment: ZOOKEEPER-2378.patch This patch moves from 2.2.0 to 2.4.0 (current version). I tested it out and it seems to build the release just fine. > upgrade ivy to recent version > - > > Key: ZOOKEEPER-2378 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 > Project: ZooKeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.4.8, 3.5.1, 3.6.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.4.9, 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2378.patch > > > 2.4.0 is the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2378) upgrade ivy to recent version
Patrick Hunt created ZOOKEEPER-2378: --- Summary: upgrade ivy to recent version Key: ZOOKEEPER-2378 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2378 Project: ZooKeeper Issue Type: Improvement Components: build Affects Versions: 3.5.1, 3.4.8, 3.6.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Critical Fix For: 3.4.9, 3.5.2, 3.6.0 2.4.0 is the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2377) zkServer.sh should resolve canonical path from symlinks
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177363#comment-15177363
]
Siddhartha commented on ZOOKEEPER-2377:
---
2) Haha yes, left over from my testing sessions, sorry.
4) Good point.
Keeping in mind that this feature did not even exist till now, we can choose to
support one degree symlinks only. In that case, we do not even have to use
readline as ls -l will be sufficient.
Alternatively, if we want to now start supporting multiple symlink traversals,
then we can retain readlink -f usage. Though of course as you pointed out, this
will lead to difference in behaviour across different platforms.
If Zookeeper has a policy to behave strictly the same across all platforms,
then I think we should go with simple one step symlink support only. Otherwise
readline -f is a neat feature to support and I think we should have that. So
your call :)
Implementing our own readlink function sounds overkill to me :P
{quote}
Last but not least, I personally like to append a ".n", where n > 1, just
before the ".patch" suffix. It makes easy to quickly glance over which patch is
the latest one and doesn't break Jenkins. Just a suggestion.
{quote}
Thanks, will follow henceforth. I was just following
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute, where it
says:
bq. In this case the updated patch should be re-attached to the Jira with the
same name. Jira will archive the older version of the patch and make the new
patch the active patch.
This page should be updated with above instructions :)
Thanks for testing and the review.
> zkServer.sh should resolve canonical path from symlinks
> ---
>
> Key: ZOOKEEPER-2377
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2377
> Project: ZooKeeper
> Issue Type: Improvement
> Components: scripts
>Affects Versions: 3.4.8
> Environment: Centos 6
>Reporter: Siddhartha
>Assignee: Siddhartha
>Priority: Minor
> Attachments: ZOOKEEPER-2377.patch, ZOOKEEPER-2377.patch
>
>
> If zkServer.sh is started from a symlink, it is not able to correctly source
> the other scripts because it looks in the wrong path.
> Attached patch fixes this by first resolving absolute path to the script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2067) Init script fails to track PID file when using a non-standard dataDir
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177303#comment-15177303 ] Hadoop QA commented on ZOOKEEPER-2067: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12677074/ZOOKEEPER-2067.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +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 appears to introduce 1 new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3074//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3074//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3074//console This message is automatically generated. > Init script fails to track PID file when using a non-standard dataDir > - > > Key: ZOOKEEPER-2067 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2067 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.4.6, 3.5.0 >Reporter: Jeremy Carroll >Assignee: Jeremy Carroll >Priority: Minor > Labels: debian > Attachments: ZOOKEEPER-2067.patch > > > When setting a dataDir in zoo.cfg that does not match /var/lib/zookeeper, the > supplied init.d script failed to track the PID file. This change moves the > logic that is present in zkServer.sh to determine the PID location into > zkEnv.sh. Also removed the hard coded path for the zookeeper dataDir. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2067 PreCommit Build #3074
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2067 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3074/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 389047 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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 failed 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/3074//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3074//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3074//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] 7ec14b2629eab218413a239537dbbfe04306734f logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 3 Total time: 15 minutes 27 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2067 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2133) zkperl: Segmentation fault if getting a node with null value
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177296#comment-15177296
]
Hadoop QA commented on ZOOKEEPER-2133:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12702849/ZOOKEEPER-2133.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 appears to introduce 1 new Findbugs (version 2.0.3)
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/3070//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3070//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3070//console
This message is automatically generated.
> zkperl: Segmentation fault if getting a node with null value
>
>
> Key: ZOOKEEPER-2133
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2133
> Project: ZooKeeper
> Issue Type: Bug
> Components: contrib-bindings
>Affects Versions: 3.4.6, 3.5.0
>Reporter: Botond Hejj
>Assignee: Botond Hejj
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2133.patch
>
>
> If Node content is null:
> [zk: (CONNECTED) 0] get /apps
> null
> cZxid = 0x1000d
> than
> my $data = $zk->{zkh}->get('/apps');
> causing a core dump with Segmentation fault
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2373) Licenses section missing from pom file
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt reassigned ZOOKEEPER-2373:
---
Assignee: Patrick Hunt
> Licenses section missing from pom file
> --
>
> Key: ZOOKEEPER-2373
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2373
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Flavio Junqueira
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> The pom file here:
> https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.8/zookeeper-3.4.8.pom
> should have a section like this:
> {noformat}
>
>
> The Apache Software License, Version 2.0
> http://www.apache.org/licenses/LICENSE-2.0.txt
>
> repo
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2133 PreCommit Build #3070
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2133 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3070/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 387978 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3070//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3070//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3070//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] 4e105d6db4f0c88e39a56cf9530594857debb4d1 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 17 minutes 54 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2133 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2055) Don't throw ArrayIndexOutOfBoundsException when SASL username/password isn't specified
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177295#comment-15177295
]
Hadoop QA commented on ZOOKEEPER-2055:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12673350/ZOOKEEPER-2055.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 appears to introduce 1 new Findbugs (version 2.0.3)
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/3072//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3072//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3072//console
This message is automatically generated.
> Don't throw ArrayIndexOutOfBoundsException when SASL username/password isn't
> specified
> --
>
> Key: ZOOKEEPER-2055
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2055
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Steve R
>Assignee: Steve R
>Priority: Minor
> Attachments: ZOOKEEPER-2055.patch
>
>
> When using SASLAuthenticationProvider and the jaas.conf file doesn't have a
> username and/or password for either the server or client configuration, when
> the client tries to connect via zkCli, an ArrayIndexOutOfBoundsException is
> thrown
> Example conf file:
> Server {
>org.apache.zookeeper.server.auth.DigestLoginModule required;
> };
> Client {
>org.apache.zookeeper.server.auth.DigestLoginModule required
>username="bob"
>password="bob123";
> };
> Shows the resuting information:
> INFO [main-SendThread(127.0.0.1:2181)] Client will use DIGEST-MD5 as SASL
> mechanism.
> ERROR[main-SendThread(127.0.0.1:2181)] Exception while trying to create SASL
> client: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2055 PreCommit Build #3072
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2055 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3072/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 379781 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3072//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3072//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3072//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] 42a0988b33f4c0cf4c980777be58e6ed191e4f35 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build@2/trunk/build.xml:1816: exec returned: 2 Total time: 13 minutes 34 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2055 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
Failed: ZOOKEEPER-2095 PreCommit Build #3069
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2095 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3069/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 378744 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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 failed 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/3069//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3069//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3069//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] 81b19a4b91ad325f72cfba22e2c0af814e41cbf0 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 3 Total time: 14 minutes 41 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2095 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2095) Add Systemd startup/conf files
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177283#comment-15177283
]
Hadoop QA commented on ZOOKEEPER-2095:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12688324/ZOOKEEPER-2095.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 appears to introduce 1 new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3069//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3069//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3069//console
This message is automatically generated.
> Add Systemd startup/conf files
> --
>
> Key: ZOOKEEPER-2095
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2095
> Project: ZooKeeper
> Issue Type: Improvement
> Components: contrib
>Reporter: Guillaume ALAUX
>Assignee: Guillaume ALAUX
>Priority: Minor
> Attachments: ZOOKEEPER-2095.patch
>
>
> As adoption of systemd by distributions grows, it would be nice to have
> systemd configuration and startup files for Zookeeper in the upstream tree. I
> would thus like to contribute the following patch which brings the followings
> systemd files:
> - {{sysusers.d_zookeeper.conf}}: creates {{zookeeper}} Linux system user to
> run Zookeeper
> - {{tmpfiles.d_zookeeper.conf}}: creates temporary {{/var/log/zookeeper}} and
> {{/var/lib/zookeeper} directories
> - {{zookeeper.service}}: regular systemd startup _script_
> - {{zookeeper@.service}}: systemd startup _script_ for specific use (for
> instance when Zookeeper is invoked to support some other piece of software –
> [example for
> Kafka|http://pkgbuild.com/git/aur-mirror.git/tree/kafka/systemd_kafka.service#n3],
> [example for
> Storm|http://pkgbuild.com/git/aur-mirror.git/tree/storm/systemd_storm-nimbus.service#n3])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2087) Few UX improvements in ZooInspector
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177278#comment-15177278 ] Hadoop QA commented on ZOOKEEPER-2087: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12682992/ZOOKEEPER-2087.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3073//console This message is automatically generated. > Few UX improvements in ZooInspector > --- > > Key: ZOOKEEPER-2087 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2087 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.6 >Reporter: Adam Dudczak >Assignee: Adam Dudczak >Priority: Minor > Attachments: ZOOKEEPER-2087.patch > > > A few simple changes would simplify using ZooInspector a lot. > - Alphabetical order of nodes on a tree view > - Short term caching of zookeeper nodes for faster rendering of node tree > - Add/Delete node in context menu of a node > - Keyboard shortcuts for add/deleting a node > - Logging information that ZooInspector failed to load nodeViewers -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2087 PreCommit Build #3073
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2087 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3073/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 136 lines...] [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12682992/ZOOKEEPER-2087.patch [exec] against trunk revision 1733348. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3073//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] 7575f9dd72c681f851259eba0aadf7e6ef133b25 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 1 Total time: 53 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2087 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2117) "caught end of stream", server: "Stale state" of a Zk client just after connecting
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177279#comment-15177279 ] Patrick Hunt commented on ZOOKEEPER-2117: - [~cnauroth] (et. al.) I know there's been some work recently on windows support - any insight on this? > "caught end of stream", server: "Stale state" of a Zk client just after > connecting > -- > > Key: ZOOKEEPER-2117 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2117 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.5.0 > Environment: Windows 8.1, Windows 2012, Visual Studio 2012 >Reporter: Bruno Gauthier >Priority: Critical > > Hi All, > Under WIndows 8.1 and 2012, using the ZooKeeper C client 3.5.0, when running > my ZooKeeper client, just after the ZooKeeper Client is connecting with the > ZooKeeper server, the ZooKeeper server is generating a “caught end of stream” > exception and deciding my is ZooKeeper client is not responsive: > Zookeeper.c::check_events, line 2298: ESTALE. (see log below). > This problem systematically appears if the ZooKeeper DLL is NOT link > statically with the Visual Studio debug version of the threaded runtime > library. > This is reproducible 10/10 > In clear, Windows ZooKeeper C client will works only if you link your > ZooKeeper DLL with the switch "/MTd" (see VS Studio->Project->Configuration > properties->C/C++->Code generation->runtime library) > > Thanks > > Bruno > > > ZooKeeper server log > > > 2015-02-06 13:19:57,552 [myid:vgcclustermgr] - INFO > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:31000:NIOServerCnxnFactory@197] - > Accepted socket connection from /10.1.200.237:63499 > 2015-02-06 13:19:57,553 [myid:vgcclustermgr] - INFO > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:31000:ZooKeeperServer@868] - Client > attempting to establish new session at /10.1.200.237:63499 > 2015-02-06 13:19:57,554 [myid:vgcclustermgr] - INFO > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:31000:NIOServerCnxnFactory@197] - > Accepted socket connection from /10.1.200.237:63500 > 2015-02-06 13:19:57,554 [myid:vgcclustermgr] - INFO > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:31000:ZooKeeperServer@868] - Client > attempting to establish new session at /10.1.200.237:63500 > 2015-02-06 13:19:57,555 [myid:vgcclustermgr] - INFO > [SyncThread:0:ZooKeeperServer@617] - Established session 0x14b5bfcba7b0409 > with negotiated timeout 8 for client /10.1.200.237:63499 > 2015-02-06 13:19:57,555 [myid:vgcclustermgr] - WARN > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:31000:NIOServerCnxn@357] - caught end > of stream exception > EndOfStreamException: Unable to read additional data from client sessionid > 0x14b5bfcba7b0409, likely client has closed socket > at > org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228) > at > org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208) > at java.lang.Thread.run(Thread.java:744) > 2015-02-06 13:19:57,555 [myid:vgcclustermgr] - INFO > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:31000:NIOServerCnxn@1007] - Closed > socket connection for client /10.1.200.237:63499 which had sessionid > 0x14b5bfcba7b0409 > 2015-02-06 13:19:57,559 [myid:vgcclustermgr] - INFO > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:31000:NIOServerCnxnFactory@197] - > Accepted socket connection from /10.1.200.237:63501 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1681) ZooKeeper 3.4.x can optionally use netty for nio but the pom does not declare the dep as optional
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177275#comment-15177275
]
Hadoop QA commented on ZOOKEEPER-1681:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12665883/ZOOKEEPER-1681.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 appears to introduce 1 new Findbugs (version 2.0.3)
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/3067//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3067//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3067//console
This message is automatically generated.
> ZooKeeper 3.4.x can optionally use netty for nio but the pom does not declare
> the dep as optional
> -
>
> Key: ZOOKEEPER-1681
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1681
> Project: ZooKeeper
> Issue Type: Improvement
>Affects Versions: 3.4.0, 3.4.1, 3.4.2, 3.4.4, 3.4.5
>Reporter: John Sirois
>Assignee: Stevo Slavic
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1681.patch
>
>
> For example in
> [3.4.5|http://search.maven.org/remotecontent?filepath=org/apache/zookeeper/zookeeper/3.4.5/zookeeper-3.4.5.pom]
> we see:
> {code}
> $ curl -sS
> http://search.maven.org/remotecontent?filepath=org/apache/zookeeper/zookeeper/3.4.5/zookeeper-3.4.5.pom
> | grep -B1 -A4 org.jboss.netty
>
> org.jboss.netty
> netty
> 3.2.2.Final
> compile
>
> {code}
> As a consumer I can depend on zookeeper with an exclude for
> org.jboss.netty#netty or I can let my transitive dep resolver pick a winner.
> This might be fine, except for those who might be using a more modern netty
> published under the newish io.netty groupId. With this twist you get both
> org.jboss.netty#netty;foo and io.netty#netty;bar on your classpath and
> runtime errors ensue from incompatibilities. unless you add an exclude
> against zookeeper (and clearly don't enable the zk netty nio handling.)
> I propose that this is a pom bug although this is debatable. Clearly as
> currently packaged zookeeper needs netty to compile, but I'd argue since it
> does not need netty to run, either the scope should be provided or optional
> or a zookeeper-netty lib should be broken out as an optional dependency and
> this new dep published by zookeeper can have a proper compile dependency on
> netty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-1681 PreCommit Build #3067
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1681 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3067/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 392163 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3067//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3067//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3067//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] 610a09b1e25bfffd3e5302eafebed1298cb48c7d logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 19 minutes 4 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-1681 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Resolved] (ZOOKEEPER-1869) zk server falling apart from quorum due to connection loss and couldn't connect back
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-1869. - Resolution: Unresolved Closing based on most recent comments/discussion. Please reopen/recreate if necessary. Thanks. > zk server falling apart from quorum due to connection loss and couldn't > connect back > > > Key: ZOOKEEPER-1869 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1869 > Project: ZooKeeper > Issue Type: Bug > Components: quorum >Affects Versions: 3.5.0 > Environment: Using CentOS6 for running these zookeeper servers >Reporter: Deepak Jagtap >Priority: Critical > > We have deployed zookeeper version 3.5.0.1515976, with 3 zk servers in the > quorum. > The problem we are facing is that one zookeeper server in the quorum falls > apart, and never becomes part of the cluster until we restart zookeeper > server on that node. > Our interpretation from zookeeper logs on all nodes is as follows: > (For simplicity assume S1=> zk server1, S2 => zk server2, S3 => zk server 3) > Initially S3 is the leader while S1 and S2 are followers. > S2 hits 46 sec latency while fsyncing write ahead log and results in loss of > connection with S3. > S3 in turn prints following error message: > Unexpected exception causing shutdown while sock still open > java.net.SocketTimeoutException: Read timed out > Stack trace > *** GOODBYE /169.254.1.2:47647(S2) > S2 in this case closes connection with S3(leader) and shuts down follower > with following log messages: > Closing connection to leader, exception during packet send > java.net.SocketException: Socket close > Follower@194] - shutdown called > java.lang.Exception: shutdown Follower > After this point S3 could never reestablish connection with S2 and leader > election mechanism keeps failing. S3 now keeps printing following message > repeatedly: > Cannot open channel to 2 at election address /169.254.1.2:3888 > java.net.ConnectException: Connection refused. > While S3 is in this state, S2 repeatedly keeps printing following message: > INFO > [NIOServerCxnFactory.AcceptThread:/0.0.0.0:2181:NIOServerCnxnFactory$AcceptThread@296] > - Accepted socket connection from /127.0.0.1:60667 > Exception causing close of session 0x0: ZooKeeperServer not running > Closed socket connection for client /127.0.0.1:60667 (no session established > for client) > Leader election never completes successfully and causing S2 to fall apart > from the quorum. > S2 was out of quorum for almost 1 week. > While debugging this issue, we found out that both election and peer > connection ports on S2 can't be telneted from any of the node (S1, S2, S3). > Network connectivity is not the issue. Later, we restarted the ZK server S2 > (service zookeeper-server restart) -- now we could telnet to both the ports > and S2 joined the ensemble after a leader election attempt. > Any idea what might be forcing S2 to get into a situation where it won't > accept any connections on the leader election and peer connection ports? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2319) UnresolvedAddressException cause the QuorumCnxManager.Listener exit
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2319:
Description:
Given three nodes, the leader on 2, but some issue with this machine, so I
shutdown this machine, and change the host name to another machine.
Then I start the node in the new machine, but the new node can not join.
I found the the 1 and 3's Listener thread exit.
With the code of Listener's run method:
I think we should catch UnresolvedAddressException to avoid the Listener exit.
{noformat}
@Override
public void run() {
while((!shutdown) && (numRetries < 3)){
try {
// bind and accept
receiveConnection(client);
} catch (IOException e) {
}
}
//
}
{noformat}
was:
Given three nodes, the leader on 2, but some issue with this machine, so I
shutdown this machine, and change the host name to another machine.
Then I start the node in the new machine, but the new node can not join.
I found the the 1 and 3's Listener thread exit.
With the code of Listener's run method:
I think we should catch UnresolvedAddressException to avoid the Listener exit.
@Override
public void run() {
while((!shutdown) && (numRetries < 3)){
try {
// bind and accept
receiveConnection(client);
} catch (IOException e) {
}
}
//
}
> UnresolvedAddressException cause the QuorumCnxManager.Listener exit
> ---
>
> Key: ZOOKEEPER-2319
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2319
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Zhaohui Yu
>Priority: Critical
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> Given three nodes, the leader on 2, but some issue with this machine, so I
> shutdown this machine, and change the host name to another machine.
> Then I start the node in the new machine, but the new node can not join.
> I found the the 1 and 3's Listener thread exit.
> With the code of Listener's run method:
> I think we should catch UnresolvedAddressException to avoid the Listener exit.
> {noformat}
> @Override
> public void run() {
>
> while((!shutdown) && (numRetries < 3)){
> try {
>// bind and accept
> receiveConnection(client);
>
> } catch (IOException e) {
>
> }
> }
> //
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1106) mt c client core when create node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177269#comment-15177269 ] Hadoop QA commented on ZOOKEEPER-1106: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12493262/patch.txt against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3071//console This message is automatically generated. > mt c client core when create node > -- > > Key: ZOOKEEPER-1106 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1106 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.3.2 >Reporter: jiang guangran >Assignee: jiang guangran > Attachments: patch.txt > > > in deserialize_CreateResponse >rc = rc ? : in->deserialize_String(in, "path", >path); >in deserialize_String > len = -1 > so v->path is uninitialised, and free, so core > do_io thread > #0 0x0039fb030265 in raise () from /lib64/libc.so.6 > #1 0x0039fb031d10 in abort () from /lib64/libc.so.6 > #2 0x0039fb06a84b in __libc_message () from /lib64/libc.so.6 > #3 0x0039fb0722ef in _int_free () from /lib64/libc.so.6 > #4 0x0039fb07273b in free () from /lib64/libc.so.6 > #5 0x2b0afd755dd1 in deallocate_String (s=0x5a490f40) at > src/recordio.c:29 > #6 0x2b0afd754ade in zookeeper_process (zh=0x131e3870, events= optimized out>) at src/zookeeper.c:2071 > #7 0x2b0afd75b2ef in do_io (v=) at > src/mt_adaptor.c:310 > #8 0x0039fb8064a7 in start_thread () from /lib64/libpthread.so.0 > #9 0x0039fb0d3c2d in clone () from /lib64/libc.so.6 > create_node thread > #0 0x0039fb80ab99 in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib64/libpthread.so.0 > #1 0x2b0afd75af5c in wait_sync_completion (sc=0x131e4c90) at > src/mt_adaptor.c:82 > #2 0x2b0afd751750 in zoo_create (zh=0x131e3870, path=0x13206fa8 > "/jsq/zr2/hb/10.250.8.139:8102", > value=0x131e86a8 > "\n\021\061\060.250.8.139:8102\022\035/home/shaoqiang/workdir2/qrs/\030\001 > \001*%\n\020\n", > valuelen=102, acl=0x2b0afd961700, flags=1, path_buffer=0x0, > path_buffer_len=0) at src/zookeeper.c:3028 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-1106 PreCommit Build #3071
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1106 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3071/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 102 lines...] [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12493262/patch.txt [exec] against trunk revision 1733348. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3071//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] fe30075957d50bcc80634e9e2f7e42882af91f2e logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 1 Total time: 46 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-1106 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Updated] (ZOOKEEPER-2319) UnresolvedAddressException cause the QuorumCnxManager.Listener exit
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2319:
Fix Version/s: 3.6.0
3.5.2
3.4.9
> UnresolvedAddressException cause the QuorumCnxManager.Listener exit
> ---
>
> Key: ZOOKEEPER-2319
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2319
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Zhaohui Yu
>Priority: Critical
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> Given three nodes, the leader on 2, but some issue with this machine, so I
> shutdown this machine, and change the host name to another machine.
> Then I start the node in the new machine, but the new node can not join.
> I found the the 1 and 3's Listener thread exit.
> With the code of Listener's run method:
> I think we should catch UnresolvedAddressException to avoid the Listener exit.
> @Override
> public void run() {
>
> while((!shutdown) && (numRetries < 3)){
> try {
>// bind and accept
> receiveConnection(client);
>
> } catch (IOException e) {
>
> }
> }
> //
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2319) UnresolvedAddressException cause the QuorumCnxManager.Listener exit
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177266#comment-15177266
]
Patrick Hunt commented on ZOOKEEPER-2319:
-
[~rgs] / [~fpj] / [~rakesh_r] is this something we can close out due to the
recent improvements in thread handling? e.g. ZOOKEEPER-1907
It's listed as a critical bug so we should consider addressing for 3.4.9 (?).
> UnresolvedAddressException cause the QuorumCnxManager.Listener exit
> ---
>
> Key: ZOOKEEPER-2319
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2319
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Zhaohui Yu
>Priority: Critical
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> Given three nodes, the leader on 2, but some issue with this machine, so I
> shutdown this machine, and change the host name to another machine.
> Then I start the node in the new machine, but the new node can not join.
> I found the the 1 and 3's Listener thread exit.
> With the code of Listener's run method:
> I think we should catch UnresolvedAddressException to avoid the Listener exit.
> @Override
> public void run() {
>
> while((!shutdown) && (numRetries < 3)){
> try {
>// bind and accept
> receiveConnection(client);
>
> } catch (IOException e) {
>
> }
> }
> //
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2374) Can not telnet 2181 port on aws ec2 server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2374: Component/s: server > Can not telnet 2181 port on aws ec2 server > -- > > Key: ZOOKEEPER-2374 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2374 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.4.6 >Reporter: zhupengfei >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > > This is the second time I faced the problem on ec2, my activemq stomp port > have the same problem, but tcp message port works fine. > I have checked zookeeper.out, no error log found. And aws technical support > tell it maybe caused by zookeeper. > OS Type: > Amazon Linux AMI > Network Test Result: > -bash-4.1$ netstat | grep 2181 > -bash-4.1$ telnet localhost 2181 > Trying 127.0.0.1... > ^C > -bash-4.1$ netstat -tunpl|grep 2181 > (Not all processes could be identified, non-owned process info > will not be shown, you would have to be root to see it all.) > tcp0 0 :::2181 :::* > LISTEN 17923/java > -bash-4.1$ netstat -an |grep 2181 > tcp0 1 172.12.10.152:60171 172.12.10.152:2181 > SYN_SENT > tcp0 0 :::2181 :::* > LISTEN > tcp0 1 :::127.0.0.1:36032 :::127.0.0.1:2181 > SYN_SENT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2103 PreCommit Build #3068
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2103 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3068/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 155 lines...] [exec] patching file src/java/test/org/apache/zookeeper/test/NettyNettySuiteTest.java [exec] patching file src/java/test/org/apache/zookeeper/test/SaslClientTest.java [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12690650/zookeeper-2103.patch [exec] against trunk revision 1733348. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 24 new or modified tests. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3068//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] 66f8cb145cff82a35793c73a0d80756687e54033 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 1 Total time: 49 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2103 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2374) Can not telnet 2181 port on aws ec2 server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177255#comment-15177255 ] Patrick Hunt commented on ZOOKEEPER-2374: - Hi [~zhufeizzz] - any update on this? Were you able to root cause it? > Can not telnet 2181 port on aws ec2 server > -- > > Key: ZOOKEEPER-2374 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2374 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.4.6 >Reporter: zhupengfei >Priority: Blocker > > This is the second time I faced the problem on ec2, my activemq stomp port > have the same problem, but tcp message port works fine. > I have checked zookeeper.out, no error log found. And aws technical support > tell it maybe caused by zookeeper. > OS Type: > Amazon Linux AMI > Network Test Result: > -bash-4.1$ netstat | grep 2181 > -bash-4.1$ telnet localhost 2181 > Trying 127.0.0.1... > ^C > -bash-4.1$ netstat -tunpl|grep 2181 > (Not all processes could be identified, non-owned process info > will not be shown, you would have to be root to see it all.) > tcp0 0 :::2181 :::* > LISTEN 17923/java > -bash-4.1$ netstat -an |grep 2181 > tcp0 1 172.12.10.152:60171 172.12.10.152:2181 > SYN_SENT > tcp0 0 :::2181 :::* > LISTEN > tcp0 1 :::127.0.0.1:36032 :::127.0.0.1:2181 > SYN_SENT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2374) Can not telnet 2181 port on aws ec2 server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2374: Fix Version/s: 3.6.0 3.5.2 3.4.9 > Can not telnet 2181 port on aws ec2 server > -- > > Key: ZOOKEEPER-2374 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2374 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.4.6 >Reporter: zhupengfei >Priority: Blocker > Fix For: 3.4.9, 3.5.2, 3.6.0 > > > This is the second time I faced the problem on ec2, my activemq stomp port > have the same problem, but tcp message port works fine. > I have checked zookeeper.out, no error log found. And aws technical support > tell it maybe caused by zookeeper. > OS Type: > Amazon Linux AMI > Network Test Result: > -bash-4.1$ netstat | grep 2181 > -bash-4.1$ telnet localhost 2181 > Trying 127.0.0.1... > ^C > -bash-4.1$ netstat -tunpl|grep 2181 > (Not all processes could be identified, non-owned process info > will not be shown, you would have to be root to see it all.) > tcp0 0 :::2181 :::* > LISTEN 17923/java > -bash-4.1$ netstat -an |grep 2181 > tcp0 1 172.12.10.152:60171 172.12.10.152:2181 > SYN_SENT > tcp0 0 :::2181 :::* > LISTEN > tcp0 1 :::127.0.0.1:36032 :::127.0.0.1:2181 > SYN_SENT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2103) ZooKeeper Client Configuration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177258#comment-15177258 ] Hadoop QA commented on ZOOKEEPER-2103: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12690650/zookeeper-2103.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 24 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3068//console This message is automatically generated. > ZooKeeper Client Configuration > -- > > Key: ZOOKEEPER-2103 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2103 > Project: ZooKeeper > Issue Type: New Feature > Components: java client >Affects Versions: 3.6.0 > Environment: All >Reporter: Chris Larsen >Assignee: Chris Larsen >Priority: Minor > Labels: features, patch > Fix For: 3.6.0 > > Attachments: zookeeper-2103.patch > > > I ran into an issue when connecting to two ZooKeeper clusters from the same > JVM application. One of the clusters required SASL authentication while the > other one did not. Unfortunately the client uses System properties to > configure authentication and the client was attempting to authenticate on the > non-auth cluster, preventing a connection. > To solve it, I implemented a base config class with helper methods for > parsing config settings as well as a client specific subclass that parsed the > system system values but allowed for overriding via programatic values or via > a file. There are also new Zookeeper constructors to use this config object. > I implemented it so that it's completely backwards compatible so it shouldn't > break existing installs (and it hasn't yet with my testing). > If folks like this, we could use the same config base for server configs and > migrate away from system properties to per object configs. It would also be > helpful to centralize more of the "zookeeper.*" strings. > Let me know what ya'll think and thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1106) mt c client core when create node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1106: Assignee: jiang guangran > mt c client core when create node > -- > > Key: ZOOKEEPER-1106 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1106 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.3.2 >Reporter: jiang guangran >Assignee: jiang guangran > Attachments: patch.txt > > > in deserialize_CreateResponse >rc = rc ? : in->deserialize_String(in, "path", >path); >in deserialize_String > len = -1 > so v->path is uninitialised, and free, so core > do_io thread > #0 0x0039fb030265 in raise () from /lib64/libc.so.6 > #1 0x0039fb031d10 in abort () from /lib64/libc.so.6 > #2 0x0039fb06a84b in __libc_message () from /lib64/libc.so.6 > #3 0x0039fb0722ef in _int_free () from /lib64/libc.so.6 > #4 0x0039fb07273b in free () from /lib64/libc.so.6 > #5 0x2b0afd755dd1 in deallocate_String (s=0x5a490f40) at > src/recordio.c:29 > #6 0x2b0afd754ade in zookeeper_process (zh=0x131e3870, events= optimized out>) at src/zookeeper.c:2071 > #7 0x2b0afd75b2ef in do_io (v=) at > src/mt_adaptor.c:310 > #8 0x0039fb8064a7 in start_thread () from /lib64/libpthread.so.0 > #9 0x0039fb0d3c2d in clone () from /lib64/libc.so.6 > create_node thread > #0 0x0039fb80ab99 in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib64/libpthread.so.0 > #1 0x2b0afd75af5c in wait_sync_completion (sc=0x131e4c90) at > src/mt_adaptor.c:82 > #2 0x2b0afd751750 in zoo_create (zh=0x131e3870, path=0x13206fa8 > "/jsq/zr2/hb/10.250.8.139:8102", > value=0x131e86a8 > "\n\021\061\060.250.8.139:8102\022\035/home/shaoqiang/workdir2/qrs/\030\001 > \001*%\n\020\n", > valuelen=102, acl=0x2b0afd961700, flags=1, path_buffer=0x0, > path_buffer_len=0) at src/zookeeper.c:3028 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2067) Init script fails to track PID file when using a non-standard dataDir
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2067: Assignee: Jeremy Carroll > Init script fails to track PID file when using a non-standard dataDir > - > > Key: ZOOKEEPER-2067 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2067 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.4.6, 3.5.0 >Reporter: Jeremy Carroll >Assignee: Jeremy Carroll >Priority: Minor > Labels: debian > Attachments: ZOOKEEPER-2067.patch > > > When setting a dataDir in zoo.cfg that does not match /var/lib/zookeeper, the > supplied init.d script failed to track the PID file. This change moves the > logic that is present in zkServer.sh to determine the PID location into > zkEnv.sh. Also removed the hard coded path for the zookeeper dataDir. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2055) Don't throw ArrayIndexOutOfBoundsException when SASL username/password isn't specified
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2055:
Assignee: Steve R
> Don't throw ArrayIndexOutOfBoundsException when SASL username/password isn't
> specified
> --
>
> Key: ZOOKEEPER-2055
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2055
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Steve R
>Assignee: Steve R
>Priority: Minor
> Attachments: ZOOKEEPER-2055.patch
>
>
> When using SASLAuthenticationProvider and the jaas.conf file doesn't have a
> username and/or password for either the server or client configuration, when
> the client tries to connect via zkCli, an ArrayIndexOutOfBoundsException is
> thrown
> Example conf file:
> Server {
>org.apache.zookeeper.server.auth.DigestLoginModule required;
> };
> Client {
>org.apache.zookeeper.server.auth.DigestLoginModule required
>username="bob"
>password="bob123";
> };
> Shows the resuting information:
> INFO [main-SendThread(127.0.0.1:2181)] Client will use DIGEST-MD5 as SASL
> mechanism.
> ERROR[main-SendThread(127.0.0.1:2181)] Exception while trying to create SASL
> client: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2087) Few UX improvements in ZooInspector
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2087: Assignee: Adam Dudczak (was: Thomas Dudziak) > Few UX improvements in ZooInspector > --- > > Key: ZOOKEEPER-2087 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2087 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.6 >Reporter: Adam Dudczak >Assignee: Adam Dudczak >Priority: Minor > Attachments: ZOOKEEPER-2087.patch > > > A few simple changes would simplify using ZooInspector a lot. > - Alphabetical order of nodes on a tree view > - Short term caching of zookeeper nodes for faster rendering of node tree > - Add/Delete node in context menu of a node > - Keyboard shortcuts for add/deleting a node > - Logging information that ZooInspector failed to load nodeViewers -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2087) Few UX improvements in ZooInspector
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2087: Assignee: Thomas Dudziak > Few UX improvements in ZooInspector > --- > > Key: ZOOKEEPER-2087 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2087 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.6 >Reporter: Adam Dudczak >Assignee: Thomas Dudziak >Priority: Minor > Attachments: ZOOKEEPER-2087.patch > > > A few simple changes would simplify using ZooInspector a lot. > - Alphabetical order of nodes on a tree view > - Short term caching of zookeeper nodes for faster rendering of node tree > - Add/Delete node in context menu of a node > - Keyboard shortcuts for add/deleting a node > - Logging information that ZooInspector failed to load nodeViewers -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2103) ZooKeeper Client Configuration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2103: Assignee: Chris Larsen > ZooKeeper Client Configuration > -- > > Key: ZOOKEEPER-2103 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2103 > Project: ZooKeeper > Issue Type: New Feature > Components: java client >Affects Versions: 3.6.0 > Environment: All >Reporter: Chris Larsen >Assignee: Chris Larsen >Priority: Minor > Labels: features, patch > Fix For: 3.6.0 > > Attachments: zookeeper-2103.patch > > > I ran into an issue when connecting to two ZooKeeper clusters from the same > JVM application. One of the clusters required SASL authentication while the > other one did not. Unfortunately the client uses System properties to > configure authentication and the client was attempting to authenticate on the > non-auth cluster, preventing a connection. > To solve it, I implemented a base config class with helper methods for > parsing config settings as well as a client specific subclass that parsed the > system system values but allowed for overriding via programatic values or via > a file. There are also new Zookeeper constructors to use this config object. > I implemented it so that it's completely backwards compatible so it shouldn't > break existing installs (and it hasn't yet with my testing). > If folks like this, we could use the same config base for server configs and > migrate away from system properties to per object configs. It would also be > helpful to centralize more of the "zookeeper.*" strings. > Let me know what ya'll think and thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2133) zkperl: Segmentation fault if getting a node with null value
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2133:
Assignee: Botond Hejj
> zkperl: Segmentation fault if getting a node with null value
>
>
> Key: ZOOKEEPER-2133
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2133
> Project: ZooKeeper
> Issue Type: Bug
> Components: contrib-bindings
>Affects Versions: 3.4.6, 3.5.0
>Reporter: Botond Hejj
>Assignee: Botond Hejj
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2133.patch
>
>
> If Node content is null:
> [zk: (CONNECTED) 0] get /apps
> null
> cZxid = 0x1000d
> than
> my $data = $zk->{zkh}->get('/apps');
> causing a core dump with Segmentation fault
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2128) zoo_aremove_watchers API is incorrect
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2128: Assignee: Dave Gosselin > zoo_aremove_watchers API is incorrect > - > > Key: ZOOKEEPER-2128 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2128 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Dave Gosselin >Assignee: Dave Gosselin > > The C API for zoo_aremove_watchers incorrectly specifies the seventh argument > as a pointer to a function pointer. It should be simply a function pointer > only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1681) ZooKeeper 3.4.x can optionally use netty for nio but the pom does not declare the dep as optional
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-1681:
Assignee: Stevo Slavic
> ZooKeeper 3.4.x can optionally use netty for nio but the pom does not declare
> the dep as optional
> -
>
> Key: ZOOKEEPER-1681
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1681
> Project: ZooKeeper
> Issue Type: Improvement
>Affects Versions: 3.4.0, 3.4.1, 3.4.2, 3.4.4, 3.4.5
>Reporter: John Sirois
>Assignee: Stevo Slavic
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1681.patch
>
>
> For example in
> [3.4.5|http://search.maven.org/remotecontent?filepath=org/apache/zookeeper/zookeeper/3.4.5/zookeeper-3.4.5.pom]
> we see:
> {code}
> $ curl -sS
> http://search.maven.org/remotecontent?filepath=org/apache/zookeeper/zookeeper/3.4.5/zookeeper-3.4.5.pom
> | grep -B1 -A4 org.jboss.netty
>
> org.jboss.netty
> netty
> 3.2.2.Final
> compile
>
> {code}
> As a consumer I can depend on zookeeper with an exclude for
> org.jboss.netty#netty or I can let my transitive dep resolver pick a winner.
> This might be fine, except for those who might be using a more modern netty
> published under the newish io.netty groupId. With this twist you get both
> org.jboss.netty#netty;foo and io.netty#netty;bar on your classpath and
> runtime errors ensue from incompatibilities. unless you add an exclude
> against zookeeper (and clearly don't enable the zk netty nio handling.)
> I propose that this is a pom bug although this is debatable. Clearly as
> currently packaged zookeeper needs netty to compile, but I'd argue since it
> does not need netty to run, either the scope should be provided or optional
> or a zookeeper-netty lib should be broken out as an optional dependency and
> this new dep published by zookeeper can have a proper compile dependency on
> netty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2095) Add Systemd startup/conf files
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2095:
Assignee: Guillaume ALAUX
> Add Systemd startup/conf files
> --
>
> Key: ZOOKEEPER-2095
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2095
> Project: ZooKeeper
> Issue Type: Improvement
> Components: contrib
>Reporter: Guillaume ALAUX
>Assignee: Guillaume ALAUX
>Priority: Minor
> Attachments: ZOOKEEPER-2095.patch
>
>
> As adoption of systemd by distributions grows, it would be nice to have
> systemd configuration and startup files for Zookeeper in the upstream tree. I
> would thus like to contribute the following patch which brings the followings
> systemd files:
> - {{sysusers.d_zookeeper.conf}}: creates {{zookeeper}} Linux system user to
> run Zookeeper
> - {{tmpfiles.d_zookeeper.conf}}: creates temporary {{/var/log/zookeeper}} and
> {{/var/lib/zookeeper} directories
> - {{zookeeper.service}}: regular systemd startup _script_
> - {{zookeeper@.service}}: systemd startup _script_ for specific use (for
> instance when Zookeeper is invoked to support some other piece of software –
> [example for
> Kafka|http://pkgbuild.com/git/aur-mirror.git/tree/kafka/systemd_kafka.service#n3],
> [example for
> Storm|http://pkgbuild.com/git/aur-mirror.git/tree/storm/systemd_storm-nimbus.service#n3])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2162) infinite exception loop occurs when dataDir is lost
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177159#comment-15177159
]
Akihiro Suda commented on ZOOKEEPER-2162:
-
The test failure seems unrelated to my change
> infinite exception loop occurs when dataDir is lost
> ---
>
> Key: ZOOKEEPER-2162
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2162
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.5.0
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
> Attachments: ZOOKEEPER-2162-v2-repro-only.log,
> ZOOKEEPER-2162-v2-repro-only.patch, ZOOKEEPER-2162-v3.patch,
> ZOOKEEPER-2162-v4.patch, ZOOKEEPER-2162.patch
>
>
> This sequence leads server.1 and server.2 to infinite exception loop.
> * Start server.1 and server.2 with the initial ensemble
> server.1=participant, server.2=observer.
>In this time, acceptedEpoch\[i\] == currentEpoch\[i\] == 1 for i = 1, 2.
> * Invoke reconfig so that acceptedEpoch\[i\] and currentEpoch\[i\] grows up
> to 2.
> * Kill server.2
> * Remove dataDir of server.2 excluding the myid file.
>(In real production environments, both of confDir and dataDir can be lost
> due to reprovisioning)
> * Start server.2
> * server.1 and server.2 enters infinite exception loop.
>The log (threshold is set to INFO in log4j.properties) size can reach >
> 100MB in 30 seconds.
> AFAIK, the bug can be reproduced with
> ZooKeeper@f5fb50ed2591ba9a24685a227bb5374759516828 (Apr 7, 2015).
> I made a Docker container so that people who are interested can reproduce the
> bug easily. (Sorry for no JUnit test right now)
> {noformat}
> $ docker run -i -t --rm akihirosuda/zookeeper-bug01
> Reproducing the bug: infinite exception loop occurs when dataDir is lost
> * Resetting
> * Starting [1,2] with the initial ensemble [1]
> * Sleeping for 3 seconds
> * Invoking Reconfig [1]->[2]
> * Sleeping for 3 seconds
> * Killing server.2 (pid=10542)
> * Sleeping for 3 seconds
> * Resetting /zk02_data
> * Starting server.2
> * Sleeping for 30 seconds
> /zk01_log: 81665114 bytes
> The log dir is extremely large. Perhaps the bug was REPRODUCED!
> /zk02_log: 23949367 bytes
> The log dir is extremely large. Perhaps the bug was REPRODUCED!
> * Exiting
> {noformat}
> h2. Log
> h3. server.1
> {noformat}
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1022]
> - FOLLOWING
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@825]
> - minSessionTimeout set to 4000
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@834]
> - maxSessionTimeout set to 4
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156]
> - Created server with tickTime 2000 minSession
> Timeout 4000 maxSessionTimeout 4 datadir /zk01_data/version-2 snapdir
> /zk01_data/version-2
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@66]
> - FOLLOWING - LEADER ELECTION TOOK - 0
> 2015-04-13 03:48:17,625 [myid:1] - WARN
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@93]
> - Exception when following the leader
> java.io.IOException: Leaders epoch, 1 is less than accepted epoch, 2
> at
> org.apache.zookeeper.server.quorum.Learner.registerWithLeader(Learner.java:331)
> at
> org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:75)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1024)
> 2015-04-13 03:48:17,626 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):MBeanRegistry@119]
> - Unregister MBean [org.apache.ZooKeeperService:
> name0=ReplicatedServer_id1,name1=replica.1,name2=Follower]
> 2015-04-13 03:48:17,626 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@198]
> - shutdown called
> java.lang.Exception: shutdown Follower
> at
> org.apache.zookeeper.server.quorum.Follower.shutdown(Follower.java:198)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1028)
> 2015-04-13 03:48:17,626 [myid:1] - DEBUG
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):LearnerZooKeeperServer@162]
> - ZooKeeper server is not running, so n
> ot proceeding to shutdown!
> 2015-04-13 03:48:17,626 [myid:1] - WARN
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1071]
> - PeerState set to
[jira] [Commented] (ZOOKEEPER-1015) DateFormat.getDateTimeInstance() is very expensive, we can cache it to improve performance
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177044#comment-15177044
]
Hadoop QA commented on ZOOKEEPER-1015:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12641564/ZOOKEEPER-1015.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 appears to introduce 1 new Findbugs (version 2.0.3)
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/3065//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3065//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3065//console
This message is automatically generated.
> DateFormat.getDateTimeInstance() is very expensive, we can cache it to
> improve performance
> --
>
> Key: ZOOKEEPER-1015
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1015
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.2
>Reporter: Xiaoming Shi
>Assignee: Bill Havanki
> Labels: newbie
> Attachments: ZOOKEEPER-1015.patch
>
>
> In the file
> {noformat}
> ./zookeeper-3.3.2/src/java/main/org/apache/zookeeper/server/PurgeTxnLog.java
> line:103
> {noformat}
> DateFormat.getDateTimeInstance() is called many times in the for loop. We can
> cache the result and improve the performance
> This is similar to the Apache bug
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48778
> Similar code can be found:
> {noformat}
> ./zookeeper-3.3.2/src/java/main/org/apache/zookeeper/server/TraceFormatter.java
> ./zookeeper-3.3.2/src/java/main/org/apache/zookeeper/server/LogFormatter.java
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-1015 PreCommit Build #3065
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1015 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3065/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 388633 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3065//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3065//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3065//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] 28b18de30c082c43a5843b8b4aaa55b50324b460 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 23 minutes 26 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-1015 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2290) Add read/write qps metrics in monitor cmd
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177019#comment-15177019 ] Hadoop QA commented on ZOOKEEPER-2290: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12766278/ZOOKEEPER-2290-v5.patch against trunk revision 1733348. +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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3062//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3062//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3062//console This message is automatically generated. > Add read/write qps metrics in monitor cmd > - > > Key: ZOOKEEPER-2290 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2290 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.6 >Reporter: Liu Shaohui >Assignee: Liu Shaohui >Priority: Minor > Labels: monitor > Fix For: 3.6.0 > > Attachments: ZOOKEEPER-2290-v1.patch, ZOOKEEPER-2290-v2.patch, > ZOOKEEPER-2290-v3.patch, ZOOKEEPER-2290-v4.patch, ZOOKEEPER-2290-v5.patch > > > Read/write qps are important metrics to show the pressure of the cluster. We > can also use it to alert about some abuse of zookeeper. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2274 PreCommit Build #3063
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2274 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3063/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 376539 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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 failed 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/3063//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3063//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3063//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] 2725017d8050e8adb9b4946768995a7f3726bac7 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 3 Total time: 10 minutes 50 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2274 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2274) ZooKeeperServerMain is difficult to subclass for unit testing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177017#comment-15177017 ] Hadoop QA commented on ZOOKEEPER-2274: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12755455/ZOOKEEPER-2274.2.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +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 appears to introduce 1 new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3063//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3063//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3063//console This message is automatically generated. > ZooKeeperServerMain is difficult to subclass for unit testing > - > > Key: ZOOKEEPER-2274 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2274 > Project: ZooKeeper > Issue Type: Improvement > Components: server, tests >Affects Versions: 3.5.1 >Reporter: Jordan Zimmerman >Assignee: Jordan Zimmerman > Attachments: ZOOKEEPER-2274.2.patch, ZOOKEEPER-2274.patch > > > Apache Curator needs a testable version of ZooKeeperServerMain. In the past, > Curator has used javassist, reflection, etc. but this is all clumsy. With a > few trivial changes, Curator could use ZooKeeperServerMain directly by > subclassing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2255) Use static member classes when permitted
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177016#comment-15177016 ] Hadoop QA commented on ZOOKEEPER-2255: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12751536/ZOOKEEPER-2255.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 99 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3066//console This message is automatically generated. > Use static member classes when permitted > > > Key: ZOOKEEPER-2255 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2255 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Yvonne Ironberg >Assignee: Yvonne Ironberg >Priority: Minor > Attachments: ZOOKEEPER-2255.patch > > > Using static member classes saves time and space because an instances of a > nonstatic member class has a reference to its enclosing instance. > Also did some style improvements: > - JLS recommends modifiers be in this order: public protected private > abstract static final transient volatile synchronized native strictfp. > - Inserted some spaces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2255 PreCommit Build #3066
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2255 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3066/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 1585 lines...] [exec] patching file src/recipes/lock/test/org/apache/zookeeper/recipes/lock/WriteLockTest.java [exec] patching file src/recipes/queue/src/java/org/apache/zookeeper/recipes/queue/DistributedQueue.java [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12751536/ZOOKEEPER-2255.patch [exec] against trunk revision 1733348. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 99 new or modified tests. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3066//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] cbb9e05abd016d39ee1d981c47f885bb995b75d4 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build@2/trunk/build.xml:1816: exec returned: 1 Total time: 48 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2255 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2275) Fix RPM package creation on recent distros
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177005#comment-15177005 ] Hadoop QA commented on ZOOKEEPER-2275: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12755818/pkg_fixes.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3064//console This message is automatically generated. > Fix RPM package creation on recent distros > -- > > Key: ZOOKEEPER-2275 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2275 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 >Reporter: Hannu Valtonen >Assignee: Hannu Valtonen > Attachments: pkg_fixes.patch > > > Three issues with RPM package building, > The install stage was removing BUILDROOT content: > [rpm] + rm -rf /tmp/zkpython_build_rpm/BUILD > Since BUILD and BUILDROOT are actually the same folder, everything is > removed before being used. > The original fix for this problem was submitted by Cédric Lejeune > http://mail-archives.apache.org/mod_mbox/zookeeper-user/201212.mbox/%3c50d2d481.8010...@pt-consulting.eu%3E > The other two issues that need to be fixed are an invalid argument given to > popd and a reference to old redhat RPM packaging scripts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2275 PreCommit Build #3064
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2275 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3064/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 184 lines...] [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12755818/pkg_fixes.patch [exec] against trunk revision 1733348. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3064//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] 90222926b59defc981894865633b6c0cd4c490e5 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 1 Total time: 1 minute 2 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2275 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2101) Transaction larger than max buffer of jute makes zookeeper unavailable
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177001#comment-15177001
]
Hadoop QA commented on ZOOKEEPER-2101:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12774993/ZOOKEEPER-2101-v8.diff
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 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 appears to introduce 1 new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3061//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3061//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3061//console
This message is automatically generated.
> Transaction larger than max buffer of jute makes zookeeper unavailable
> --
>
> Key: ZOOKEEPER-2101
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2101
> Project: ZooKeeper
> Issue Type: Bug
> Components: jute
>Affects Versions: 3.4.4
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2101-v1.diff, ZOOKEEPER-2101-v2.diff,
> ZOOKEEPER-2101-v3.diff, ZOOKEEPER-2101-v4.diff, ZOOKEEPER-2101-v5.diff,
> ZOOKEEPER-2101-v6.diff, ZOOKEEPER-2101-v7.diff, ZOOKEEPER-2101-v8.diff,
> test.diff
>
>
> *Problem*
> For multi operation, PrepRequestProcessor may produce a large transaction
> whose size may be larger than the max buffer size of jute. There is check of
> buffer size in readBuffer method of BinaryInputArchive, but no check in
> writeBuffer method of BinaryOutputArchive, which will cause that
> 1, Leader can sync transaction to txn log and send the large transaction to
> the followers, but the followers failed to read the transaction and can't
> sync with leader.
> {code}
> 2015-01-04,12:42:26,474 WARN org.apache.zookeeper.server.quorum.Learner:
> [myid:2] Exception when following the leader
> java.io.IOException: Unreasonable length = 2054758
> at
> org.apache.jute.BinaryInputArchive.readBuffer(BinaryInputArchive.java:100)
> at
> org.apache.zookeeper.server.quorum.QuorumPacket.deserialize(QuorumPacket.java:85)
> at
> org.apache.jute.BinaryInputArchive.readRecord(BinaryInputArchive.java:108)
> at
> org.apache.zookeeper.server.quorum.Learner.readPacket(Learner.java:152)
> at
> org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:85)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:740)
> 2015-01-04,12:42:26,475 INFO org.apache.zookeeper.server.quorum.Learner:
> [myid:2] shutdown called
> java.lang.Exception: shutdown Follower
> at
> org.apache.zookeeper.server.quorum.Follower.shutdown(Follower.java:166)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:744)
> {code}
> 2, The leader lose all followers, which trigger the leader election. The old
> leader will become leader again for it has up-to-date data.
> {code}
> 2015-01-04,12:42:28,502 INFO org.apache.zookeeper.server.quorum.Leader:
> [myid:3] Shutting down
> 2015-01-04,12:42:28,502 INFO org.apache.zookeeper.server.quorum.Leader:
> [myid:3] Shutdown called
> java.lang.Exception: shutdown Leader! reason: Only 1 followers, need 2
> at org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:496)
> at org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:471)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:753)
> {code}
> 3, The leader can not load the transaction from the txn log for the length of
> data is larger than the max buffer of jute.
> {code}
> 2015-01-04,12:42:31,282 ERROR org.apache.zookeeper.server.quorum.QuorumPeer:
> [myid:3] Unable to load database on disk
> java.io.IOException: Unreasonable length = 2054758
> at
> org.apache.jute.BinaryInputArchive.readBuffer(BinaryInputArchive.java:100)
> at
> org.apache.zookeeper.server.persistence.Util.readTxnBytes(Util.java:233)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.next(FileTxnLog.java:602)
> at
>
Failed: ZOOKEEPER-2162 PreCommit Build #3059
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2162 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3059/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 348696 lines...] [exec] [exec] +1 tests included. The patch appears to include 5 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 appears to introduce 2 new Findbugs (version 2.0.3) 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 failed 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/3059//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3059//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3059//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] 147fea079f4a8df59ebd7b80efd5c8e5fea53b44 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 18 minutes 16 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Compressed 553.85 KB of artifacts by 23.1% relative to #3049 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2162 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## 2 tests failed. FAILED: org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig Error Message: waiting for server 2 being up Stack Trace: junit.framework.AssertionFailedError: waiting for server 2 being up at org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79) FAILED: org.apache.zookeeper.test.SSLTest.testSecureQuorumServer Error Message: waiting for server 0 being up Stack Trace: junit.framework.AssertionFailedError: waiting for server 0 being up at org.apache.zookeeper.test.SSLTest.testSecureQuorumServer(SSLTest.java:99) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
[jira] [Commented] (ZOOKEEPER-2162) infinite exception loop occurs when dataDir is lost
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177002#comment-15177002
]
Hadoop QA commented on ZOOKEEPER-2162:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12776043/ZOOKEEPER-2162-v4.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 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 appears to introduce 2 new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3059//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3059//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3059//console
This message is automatically generated.
> infinite exception loop occurs when dataDir is lost
> ---
>
> Key: ZOOKEEPER-2162
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2162
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.5.0
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
> Attachments: ZOOKEEPER-2162-v2-repro-only.log,
> ZOOKEEPER-2162-v2-repro-only.patch, ZOOKEEPER-2162-v3.patch,
> ZOOKEEPER-2162-v4.patch, ZOOKEEPER-2162.patch
>
>
> This sequence leads server.1 and server.2 to infinite exception loop.
> * Start server.1 and server.2 with the initial ensemble
> server.1=participant, server.2=observer.
>In this time, acceptedEpoch\[i\] == currentEpoch\[i\] == 1 for i = 1, 2.
> * Invoke reconfig so that acceptedEpoch\[i\] and currentEpoch\[i\] grows up
> to 2.
> * Kill server.2
> * Remove dataDir of server.2 excluding the myid file.
>(In real production environments, both of confDir and dataDir can be lost
> due to reprovisioning)
> * Start server.2
> * server.1 and server.2 enters infinite exception loop.
>The log (threshold is set to INFO in log4j.properties) size can reach >
> 100MB in 30 seconds.
> AFAIK, the bug can be reproduced with
> ZooKeeper@f5fb50ed2591ba9a24685a227bb5374759516828 (Apr 7, 2015).
> I made a Docker container so that people who are interested can reproduce the
> bug easily. (Sorry for no JUnit test right now)
> {noformat}
> $ docker run -i -t --rm akihirosuda/zookeeper-bug01
> Reproducing the bug: infinite exception loop occurs when dataDir is lost
> * Resetting
> * Starting [1,2] with the initial ensemble [1]
> * Sleeping for 3 seconds
> * Invoking Reconfig [1]->[2]
> * Sleeping for 3 seconds
> * Killing server.2 (pid=10542)
> * Sleeping for 3 seconds
> * Resetting /zk02_data
> * Starting server.2
> * Sleeping for 30 seconds
> /zk01_log: 81665114 bytes
> The log dir is extremely large. Perhaps the bug was REPRODUCED!
> /zk02_log: 23949367 bytes
> The log dir is extremely large. Perhaps the bug was REPRODUCED!
> * Exiting
> {noformat}
> h2. Log
> h3. server.1
> {noformat}
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1022]
> - FOLLOWING
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@825]
> - minSessionTimeout set to 4000
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@834]
> - maxSessionTimeout set to 4
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156]
> - Created server with tickTime 2000 minSession
> Timeout 4000 maxSessionTimeout 4 datadir /zk01_data/version-2 snapdir
> /zk01_data/version-2
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@66]
> - FOLLOWING - LEADER ELECTION TOOK - 0
> 2015-04-13 03:48:17,625 [myid:1] - WARN
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@93]
> - Exception when following the leader
> java.io.IOException: Leaders epoch, 1 is less than accepted epoch, 2
> at
> org.apache.zookeeper.server.quorum.Learner.registerWithLeader(Learner.java:331)
> at
>
Failed: ZOOKEEPER-2101 PreCommit Build #3061
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2101 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3061/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 376698 lines...] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 5 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 appears to introduce 1 new Findbugs (version 2.0.3) 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 failed 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/3061//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3061//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3061//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] 685b02d78db2e570c56e538310fa963174f0e584 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 13 minutes 42 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2101 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2202) Cluster crashes when reconfig adds an unreachable observer
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176996#comment-15176996
]
Hadoop QA commented on ZOOKEEPER-2202:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12764113/ZOOKEEPER-2202.patch
against trunk revision 1733348.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 appears to introduce 1 new Findbugs (version 2.0.3)
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/3060//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3060//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3060//console
This message is automatically generated.
> Cluster crashes when reconfig adds an unreachable observer
> --
>
> Key: ZOOKEEPER-2202
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2202
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.5.0, 3.6.0
>Reporter: Raul Gutierrez Segales
>Assignee: Raul Gutierrez Segales
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2202.patch
>
>
> While adding support for reconfig() in Kazoo
> (https://github.com/python-zk/kazoo/pull/333) I found that the cluster can be
> crashed if you add an observer whose election port isn't reachable (i.e.:
> packets for that destination are dropped, not rejected). This will raise a
> SocketTimeoutException which will bring down the PrepRequestProcessor:
> {code}
> 2015-06-02 14:37:16,473 [myid:3] - WARN [ProcessThread(sid:3
> cport:-1)::QuorumCnxManager@384] - Cannot open channel to 100 at election
> address /8.8.8.8:38703
> java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at
> org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:369)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.connectNewPeers(QuorumPeer.java:1288)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.setLastSeenQuorumVerifier(QuorumPeer.java:1315)
> at org.apache.zookeeper.server.quorum.Leader.propose(Leader.java:1056)
> at
> org.apache.zookeeper.server.quorum.ProposalRequestProcessor.processRequest(ProposalRequestProcessor.java:78)
> at
> org.apache.zookeeper.server.PrepRequestProcessor.pRequest(PrepRequestProcessor.java:877)
> at
> org.apache.zookeeper.server.PrepRequestProcessor.run(PrepRequestProcessor.java:143)
> {code}
> A simple repro can be obtained by using the code in the referenced pull
> request above and using 8.8.8.8:3888 (for example) instead of a free (but
> closed) port in the loopback.
> I think that adding an Observer (or a Participant) that isn't currently
> reachable is a valid use case (i.e.: you are provisioning the machine and
> it's not currently needed) so I think we could handle this with lower connect
> timeouts, not sure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2202 PreCommit Build #3060
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2202 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3060/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 380169 lines...] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3060//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3060//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3060//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] 256e951633e7a469e0f7fb477a8c07d840619ae1 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 2 Total time: 14 minutes 28 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2202 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2260) Paginated getChildren call
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176976#comment-15176976 ] Hadoop QA commented on ZOOKEEPER-2260: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12777600/ZOOKEEPER-2260.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 8 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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3058//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3058//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3058//console This message is automatically generated. > Paginated getChildren call > -- > > Key: ZOOKEEPER-2260 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2260 > Project: ZooKeeper > Issue Type: New Feature >Affects Versions: 3.4.6, 3.5.0 >Reporter: Marco P. >Assignee: Marco P. > Labels: api, features > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2260.patch, ZOOKEEPER-2260.patch > > > Add pagination support to the getChildren() call, allowing clients to iterate > over children N at the time. > Motivations for this include: > - Getting out of a situation where so many children were created that > listing them exceeded the network buffer sizes (making it impossible to > recover by deleting)[1] > - More efficient traversal of nodes with large number of children [2] > I do have a patch (for 3.4.6) we've been using successfully for a while, but > I suspect much more work is needed for this to be accepted. > [1] https://issues.apache.org/jira/browse/ZOOKEEPER-272 > [2] https://issues.apache.org/jira/browse/ZOOKEEPER-282 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2260 PreCommit Build #3058
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2260 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3058/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 377153 lines...] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 8 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 appears to introduce 1 new Findbugs (version 2.0.3) 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/3058//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3058//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3058//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] d23e0a4310f364dc22727412c166592b0aaa5e23 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 1 Total time: 13 minutes 40 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2260 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Updated] (ZOOKEEPER-1015) DateFormat.getDateTimeInstance() is very expensive, we can cache it to improve performance
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-1015:
Assignee: Bill Havanki
> DateFormat.getDateTimeInstance() is very expensive, we can cache it to
> improve performance
> --
>
> Key: ZOOKEEPER-1015
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1015
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.2
>Reporter: Xiaoming Shi
>Assignee: Bill Havanki
> Labels: newbie
> Attachments: ZOOKEEPER-1015.patch
>
>
> In the file
> {noformat}
> ./zookeeper-3.3.2/src/java/main/org/apache/zookeeper/server/PurgeTxnLog.java
> line:103
> {noformat}
> DateFormat.getDateTimeInstance() is called many times in the for loop. We can
> cache the result and improve the performance
> This is similar to the Apache bug
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48778
> Similar code can be found:
> {noformat}
> ./zookeeper-3.3.2/src/java/main/org/apache/zookeeper/server/TraceFormatter.java
> ./zookeeper-3.3.2/src/java/main/org/apache/zookeeper/server/LogFormatter.java
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2255) Use static member classes when permitted
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2255: Assignee: Yvonne Ironberg > Use static member classes when permitted > > > Key: ZOOKEEPER-2255 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2255 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Yvonne Ironberg >Assignee: Yvonne Ironberg >Priority: Minor > Attachments: ZOOKEEPER-2255.patch > > > Using static member classes saves time and space because an instances of a > nonstatic member class has a reference to its enclosing instance. > Also did some style improvements: > - JLS recommends modifiers be in this order: public protected private > abstract static final transient volatile synchronized native strictfp. > - Inserted some spaces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2093 PreCommit Build #3057
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2093 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3057/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 108 lines...] [exec] patching file src/java/test/org/apache/zookeeper/test/FourLetterWordsTest.java [exec] Hunk #1 succeeded at 155 (offset 20 lines). [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12684450/export-cumulative-latency.patch [exec] against trunk revision 1733348. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 6 new or modified tests. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3057//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] 3e0ff7b16121a47a93932c954ac5633907b1dd7d logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 1 Total time: 50 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2093 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2093) Expose cumulative latency and request count
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15176950#comment-15176950 ] Hadoop QA commented on ZOOKEEPER-2093: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12684450/export-cumulative-latency.patch against trunk revision 1733348. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3057//console This message is automatically generated. > Expose cumulative latency and request count > --- > > Key: ZOOKEEPER-2093 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2093 > Project: ZooKeeper > Issue Type: Improvement > Components: jmx, server >Reporter: Brian Brazil >Assignee: Brian Brazil >Priority: Minor > Labels: patch > Fix For: 3.6.0 > > Attachments: export-cumulative-latency.patch > > > Currently Zookeeper exposes min, max and average since server start request > latency. > It'd also be useful to be able to calculate latency over a given time period. > This patch exposes the total latency, and count of number of request. By > tracking how these values increase over time, your monitoring system can > calculate the average latency over a given period of time. > This only provides milliseconds, as that's what's currently there. > I'm seeing a test failure on ClientPortBindTest.testBindByAddress, this > appears to be due to my IPv6 setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2274) ZooKeeperServerMain is difficult to subclass for unit testing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2274: Assignee: Jordan Zimmerman > ZooKeeperServerMain is difficult to subclass for unit testing > - > > Key: ZOOKEEPER-2274 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2274 > Project: ZooKeeper > Issue Type: Improvement > Components: server, tests >Affects Versions: 3.5.1 >Reporter: Jordan Zimmerman >Assignee: Jordan Zimmerman > Attachments: ZOOKEEPER-2274.2.patch, ZOOKEEPER-2274.patch > > > Apache Curator needs a testable version of ZooKeeperServerMain. In the past, > Curator has used javassist, reflection, etc. but this is all clumsy. With a > few trivial changes, Curator could use ZooKeeperServerMain directly by > subclassing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2275) Fix RPM package creation on recent distros
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2275: Assignee: Hannu Valtonen > Fix RPM package creation on recent distros > -- > > Key: ZOOKEEPER-2275 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2275 > Project: ZooKeeper > Issue Type: Bug > Components: build >Affects Versions: 3.5.1 >Reporter: Hannu Valtonen >Assignee: Hannu Valtonen > Attachments: pkg_fixes.patch > > > Three issues with RPM package building, > The install stage was removing BUILDROOT content: > [rpm] + rm -rf /tmp/zkpython_build_rpm/BUILD > Since BUILD and BUILDROOT are actually the same folder, everything is > removed before being used. > The original fix for this problem was submitted by Cédric Lejeune > http://mail-archives.apache.org/mod_mbox/zookeeper-user/201212.mbox/%3c50d2d481.8010...@pt-consulting.eu%3E > The other two issues that need to be fixed are an invalid argument given to > popd and a reference to old redhat RPM packaging scripts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2290) Add read/write qps metrics in monitor cmd
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2290: Assignee: Liu Shaohui > Add read/write qps metrics in monitor cmd > - > > Key: ZOOKEEPER-2290 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2290 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.6 >Reporter: Liu Shaohui >Assignee: Liu Shaohui >Priority: Minor > Labels: monitor > Fix For: 3.6.0 > > Attachments: ZOOKEEPER-2290-v1.patch, ZOOKEEPER-2290-v2.patch, > ZOOKEEPER-2290-v3.patch, ZOOKEEPER-2290-v4.patch, ZOOKEEPER-2290-v5.patch > > > Read/write qps are important metrics to show the pressure of the cluster. We > can also use it to alert about some abuse of zookeeper. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2101) Transaction larger than max buffer of jute makes zookeeper unavailable
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2101:
Assignee: Liu Shaohui
> Transaction larger than max buffer of jute makes zookeeper unavailable
> --
>
> Key: ZOOKEEPER-2101
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2101
> Project: ZooKeeper
> Issue Type: Bug
> Components: jute
>Affects Versions: 3.4.4
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2101-v1.diff, ZOOKEEPER-2101-v2.diff,
> ZOOKEEPER-2101-v3.diff, ZOOKEEPER-2101-v4.diff, ZOOKEEPER-2101-v5.diff,
> ZOOKEEPER-2101-v6.diff, ZOOKEEPER-2101-v7.diff, ZOOKEEPER-2101-v8.diff,
> test.diff
>
>
> *Problem*
> For multi operation, PrepRequestProcessor may produce a large transaction
> whose size may be larger than the max buffer size of jute. There is check of
> buffer size in readBuffer method of BinaryInputArchive, but no check in
> writeBuffer method of BinaryOutputArchive, which will cause that
> 1, Leader can sync transaction to txn log and send the large transaction to
> the followers, but the followers failed to read the transaction and can't
> sync with leader.
> {code}
> 2015-01-04,12:42:26,474 WARN org.apache.zookeeper.server.quorum.Learner:
> [myid:2] Exception when following the leader
> java.io.IOException: Unreasonable length = 2054758
> at
> org.apache.jute.BinaryInputArchive.readBuffer(BinaryInputArchive.java:100)
> at
> org.apache.zookeeper.server.quorum.QuorumPacket.deserialize(QuorumPacket.java:85)
> at
> org.apache.jute.BinaryInputArchive.readRecord(BinaryInputArchive.java:108)
> at
> org.apache.zookeeper.server.quorum.Learner.readPacket(Learner.java:152)
> at
> org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:85)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:740)
> 2015-01-04,12:42:26,475 INFO org.apache.zookeeper.server.quorum.Learner:
> [myid:2] shutdown called
> java.lang.Exception: shutdown Follower
> at
> org.apache.zookeeper.server.quorum.Follower.shutdown(Follower.java:166)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:744)
> {code}
> 2, The leader lose all followers, which trigger the leader election. The old
> leader will become leader again for it has up-to-date data.
> {code}
> 2015-01-04,12:42:28,502 INFO org.apache.zookeeper.server.quorum.Leader:
> [myid:3] Shutting down
> 2015-01-04,12:42:28,502 INFO org.apache.zookeeper.server.quorum.Leader:
> [myid:3] Shutdown called
> java.lang.Exception: shutdown Leader! reason: Only 1 followers, need 2
> at org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:496)
> at org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:471)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:753)
> {code}
> 3, The leader can not load the transaction from the txn log for the length of
> data is larger than the max buffer of jute.
> {code}
> 2015-01-04,12:42:31,282 ERROR org.apache.zookeeper.server.quorum.QuorumPeer:
> [myid:3] Unable to load database on disk
> java.io.IOException: Unreasonable length = 2054758
> at
> org.apache.jute.BinaryInputArchive.readBuffer(BinaryInputArchive.java:100)
> at
> org.apache.zookeeper.server.persistence.Util.readTxnBytes(Util.java:233)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.next(FileTxnLog.java:602)
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.restore(FileTxnSnapLog.java:157)
> at
> org.apache.zookeeper.server.ZKDatabase.loadDataBase(ZKDatabase.java:223)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:417)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.getLastLoggedZxid(QuorumPeer.java:546)
> at
> org.apache.zookeeper.server.quorum.FastLeaderElection.getInitLastLoggedZxid(FastLeaderElection.java:690)
> at
> org.apache.zookeeper.server.quorum.FastLeaderElection.lookForLeader(FastLeaderElection.java:737)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:716)
> {code}
> The zookeeper service will be unavailable until we enlarge the jute.maxbuffer
> and restart zookeeper hbase cluster.
> *Solution*
> Add buffer size check in BinaryOutputArchive to avoid large transaction be
> written to log and sent to followers.
> But I am not sure if there are side-effects of throwing an IOException in
> BinaryOutputArchive and RequestProcessors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2202) Cluster crashes when reconfig adds an unreachable observer
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2202:
Assignee: Raul Gutierrez Segales
> Cluster crashes when reconfig adds an unreachable observer
> --
>
> Key: ZOOKEEPER-2202
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2202
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.5.0, 3.6.0
>Reporter: Raul Gutierrez Segales
>Assignee: Raul Gutierrez Segales
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2202.patch
>
>
> While adding support for reconfig() in Kazoo
> (https://github.com/python-zk/kazoo/pull/333) I found that the cluster can be
> crashed if you add an observer whose election port isn't reachable (i.e.:
> packets for that destination are dropped, not rejected). This will raise a
> SocketTimeoutException which will bring down the PrepRequestProcessor:
> {code}
> 2015-06-02 14:37:16,473 [myid:3] - WARN [ProcessThread(sid:3
> cport:-1)::QuorumCnxManager@384] - Cannot open channel to 100 at election
> address /8.8.8.8:38703
> java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at
> org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:369)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.connectNewPeers(QuorumPeer.java:1288)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.setLastSeenQuorumVerifier(QuorumPeer.java:1315)
> at org.apache.zookeeper.server.quorum.Leader.propose(Leader.java:1056)
> at
> org.apache.zookeeper.server.quorum.ProposalRequestProcessor.processRequest(ProposalRequestProcessor.java:78)
> at
> org.apache.zookeeper.server.PrepRequestProcessor.pRequest(PrepRequestProcessor.java:877)
> at
> org.apache.zookeeper.server.PrepRequestProcessor.run(PrepRequestProcessor.java:143)
> {code}
> A simple repro can be obtained by using the code in the referenced pull
> request above and using 8.8.8.8:3888 (for example) instead of a free (but
> closed) port in the loopback.
> I think that adding an Observer (or a Participant) that isn't currently
> reachable is a valid use case (i.e.: you are provisioning the machine and
> it's not currently needed) so I think we could handle this with lower connect
> timeouts, not sure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2162) infinite exception loop occurs when dataDir is lost
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2162:
Assignee: Akihiro Suda
> infinite exception loop occurs when dataDir is lost
> ---
>
> Key: ZOOKEEPER-2162
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2162
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.5.0
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
> Attachments: ZOOKEEPER-2162-v2-repro-only.log,
> ZOOKEEPER-2162-v2-repro-only.patch, ZOOKEEPER-2162-v3.patch,
> ZOOKEEPER-2162-v4.patch, ZOOKEEPER-2162.patch
>
>
> This sequence leads server.1 and server.2 to infinite exception loop.
> * Start server.1 and server.2 with the initial ensemble
> server.1=participant, server.2=observer.
>In this time, acceptedEpoch\[i\] == currentEpoch\[i\] == 1 for i = 1, 2.
> * Invoke reconfig so that acceptedEpoch\[i\] and currentEpoch\[i\] grows up
> to 2.
> * Kill server.2
> * Remove dataDir of server.2 excluding the myid file.
>(In real production environments, both of confDir and dataDir can be lost
> due to reprovisioning)
> * Start server.2
> * server.1 and server.2 enters infinite exception loop.
>The log (threshold is set to INFO in log4j.properties) size can reach >
> 100MB in 30 seconds.
> AFAIK, the bug can be reproduced with
> ZooKeeper@f5fb50ed2591ba9a24685a227bb5374759516828 (Apr 7, 2015).
> I made a Docker container so that people who are interested can reproduce the
> bug easily. (Sorry for no JUnit test right now)
> {noformat}
> $ docker run -i -t --rm akihirosuda/zookeeper-bug01
> Reproducing the bug: infinite exception loop occurs when dataDir is lost
> * Resetting
> * Starting [1,2] with the initial ensemble [1]
> * Sleeping for 3 seconds
> * Invoking Reconfig [1]->[2]
> * Sleeping for 3 seconds
> * Killing server.2 (pid=10542)
> * Sleeping for 3 seconds
> * Resetting /zk02_data
> * Starting server.2
> * Sleeping for 30 seconds
> /zk01_log: 81665114 bytes
> The log dir is extremely large. Perhaps the bug was REPRODUCED!
> /zk02_log: 23949367 bytes
> The log dir is extremely large. Perhaps the bug was REPRODUCED!
> * Exiting
> {noformat}
> h2. Log
> h3. server.1
> {noformat}
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1022]
> - FOLLOWING
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@825]
> - minSessionTimeout set to 4000
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@834]
> - maxSessionTimeout set to 4
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156]
> - Created server with tickTime 2000 minSession
> Timeout 4000 maxSessionTimeout 4 datadir /zk01_data/version-2 snapdir
> /zk01_data/version-2
> 2015-04-13 03:48:17,624 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@66]
> - FOLLOWING - LEADER ELECTION TOOK - 0
> 2015-04-13 03:48:17,625 [myid:1] - WARN
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@93]
> - Exception when following the leader
> java.io.IOException: Leaders epoch, 1 is less than accepted epoch, 2
> at
> org.apache.zookeeper.server.quorum.Learner.registerWithLeader(Learner.java:331)
> at
> org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:75)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1024)
> 2015-04-13 03:48:17,626 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):MBeanRegistry@119]
> - Unregister MBean [org.apache.ZooKeeperService:
> name0=ReplicatedServer_id1,name1=replica.1,name2=Follower]
> 2015-04-13 03:48:17,626 [myid:1] - INFO
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@198]
> - shutdown called
> java.lang.Exception: shutdown Follower
> at
> org.apache.zookeeper.server.quorum.Follower.shutdown(Follower.java:198)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1028)
> 2015-04-13 03:48:17,626 [myid:1] - DEBUG
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):LearnerZooKeeperServer@162]
> - ZooKeeper server is not running, so n
> ot proceeding to shutdown!
> 2015-04-13 03:48:17,626 [myid:1] - WARN
> [QuorumPeer[myid=1](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1071]
> - PeerState set to LOOKING
> 2015-04-13 03:48:17,626 [myid:1] - INFO
>
[jira] [Updated] (ZOOKEEPER-2093) Expose cumulative latency and request count
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2093: Assignee: Brian Brazil > Expose cumulative latency and request count > --- > > Key: ZOOKEEPER-2093 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2093 > Project: ZooKeeper > Issue Type: Improvement > Components: jmx, server >Reporter: Brian Brazil >Assignee: Brian Brazil >Priority: Minor > Labels: patch > Fix For: 3.6.0 > > Attachments: export-cumulative-latency.patch > > > Currently Zookeeper exposes min, max and average since server start request > latency. > It'd also be useful to be able to calculate latency over a given time period. > This patch exposes the total latency, and count of number of request. By > tracking how these values increase over time, your monitoring system can > calculate the average latency over a given period of time. > This only provides milliseconds, as that's what's currently there. > I'm seeing a test failure on ClientPortBindTest.testBindByAddress, this > appears to be due to my IPv6 setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2332) Zookeeper failed to start for empty txn log
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2332:
Assignee: Liu Shaohui
> Zookeeper failed to start for empty txn log
> ---
>
> Key: ZOOKEEPER-2332
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2332
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Critical
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2332-v001.diff
>
>
> We found that the zookeeper server with version 3.4.6 failed to start for
> there is a empty txn log in log dir.
> I think we should skip the empty log file during restoring the datatree.
> Any suggestion?
> {code}
> 2015-11-27 19:16:16,887 [myid:] - ERROR [main:ZooKeeperServerMain@63] -
> Unexpected exception, exiting abnormally
> java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:392)
> at org.apache.jute.BinaryInputArchive.readInt(BinaryInputArchive.java:63)
> at
> org.apache.zookeeper.server.persistence.FileHeader.deserialize(FileHeader.java:64)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.inStreamCreated(FileTxnLog.java:576)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.createInputArchive(FileTxnLog.java:595)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.goToNextLog(FileTxnLog.java:561)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.next(FileTxnLog.java:643)
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.restore(FileTxnSnapLog.java:158)
> at org.apache.zookeeper.server.ZKDatabase.loadDataBase(ZKDatabase.java:223)
> at
> org.apache.zookeeper.server.ZooKeeperServer.loadData(ZooKeeperServer.java:272)
> at
> org.apache.zookeeper.server.ZooKeeperServer.startdata(ZooKeeperServer.java:399)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.startup(NIOServerCnxnFactory.java:122)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:113)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:86)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:52)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-954) Findbugs/ClientCnxn: Bug type JLM_JSR166_UTILCONCURRENT_MONITORENTER
[
https://issues.apache.org/jira/browse/ZOOKEEPER-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-954:
---
Assignee: Hiroshi Ikeda
> Findbugs/ClientCnxn: Bug type JLM_JSR166_UTILCONCURRENT_MONITORENTER
>
>
> Key: ZOOKEEPER-954
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-954
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
>Reporter: Thomas Koch
>Assignee: Hiroshi Ikeda
>Priority: Minor
> Attachments: ZOOKEEPER-954-V2.patch, ZOOKEEPER-954.patch
>
>
> JLM Synchronization performed on java.util.concurrent.LinkedBlockingQueue
> in org.apache.zookeeper.ClientCnxn$EventThread.queuePacket(ClientCnxn$Packet)
>
> Bug type JLM_JSR166_UTILCONCURRENT_MONITORENTER (click for details)
> In class org.apache.zookeeper.ClientCnxn$EventThread
> In method
> org.apache.zookeeper.ClientCnxn$EventThread.queuePacket(ClientCnxn$Packet)
> Type java.util.concurrent.LinkedBlockingQueue
> Value loaded from field
> org.apache.zookeeper.ClientCnxn$EventThread.waitingEvents
> At ClientCnxn.java:[line 411]
> JLM Synchronization performed on java.util.concurrent.LinkedBlockingQueue
> in org.apache.zookeeper.ClientCnxn$EventThread.run()
>
> Bug type JLM_JSR166_UTILCONCURRENT_MONITORENTER (click for details)
> In class org.apache.zookeeper.ClientCnxn$EventThread
> In method org.apache.zookeeper.ClientCnxn$EventThread.run()
> Type java.util.concurrent.LinkedBlockingQueue
> Value loaded from field
> org.apache.zookeeper.ClientCnxn$EventThread.waitingEvents
> At ClientCnxn.java:[line 436]
> The respective code:
> 409 public void queuePacket(Packet packet) {
> 410 if (wasKilled) {
> 411synchronized (waitingEvents) {
> 412 if (isRunning) waitingEvents.add(packet);
> 413 else processEvent(packet);
> 414}
> 415 } else {
> 416waitingEvents.add(packet);
> 417 }
> 418 }
> 419
> 420 public void queueEventOfDeath() {
> 421 waitingEvents.add(eventOfDeath);
> 422 }
> 423
> 424 @Override
> 425 public void run() {
> 426 try {
> 427 isRunning = true;
> 428 while (true) {
> 429Object event = waitingEvents.take();
> 430if (event == eventOfDeath) {
> 431 wasKilled = true;
> 432} else {
> 433 processEvent(event);
> 434}
> 435if (wasKilled)
> 436 synchronized (waitingEvents) {
> 437 if (waitingEvents.isEmpty()) {
> 438 isRunning = false;
> 439 break;
> 440 }
> 441 }
> 442 }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2366) Reconfiguration of client port causes a socket leak
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2366:
Assignee: Timothy Ward
> Reconfiguration of client port causes a socket leak
> ---
>
> Key: ZOOKEEPER-2366
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2366
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
>Affects Versions: 3.5.0
>Reporter: Timothy Ward
>Assignee: Timothy Ward
>Priority: Critical
> Fix For: 3.5.2
>
> Attachments: zookeeper.patch
>
>
> The NIOServerCnxnFactory reconfigure method can leak server sockets, and
> hence make ports unusable until the JVM restarts:
> The first line of the method takes a reference to the current
> ServerSocketChannel and then the next line replaces it. The subsequent
> interactions with the server socket can fail (for example if the
> reconfiguration tries to bind to an in-use port). If they fail *before* the
> call to oldSS.close() then oldSS is *never* closed. This holds that port open
> forever, and prevents the user from rolling back to the previous port!
> The code from reconfigure is shown below:
> ServerSocketChannel oldSS = ss;
> try {
>this.ss = ServerSocketChannel.open();
>ss.socket().setReuseAddress(true);
>LOG.info("binding to port " + addr);
>ss.socket().bind(addr);
>ss.configureBlocking(false);
>acceptThread.setReconfiguring();
>oldSS.close();
>acceptThread.wakeupSelector();
>try {
> acceptThread.join();
> } catch (InterruptedException e) {
> LOG.error("Error joining old acceptThread when
> reconfiguring client port " + e.getMessage());
> }
>acceptThread = new AcceptThread(ss, addr, selectorThreads);
>acceptThread.start();
> } catch(IOException e) {
>LOG.error("Error reconfiguring client port to " + addr + " " +
> e.getMessage());
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2195) fsync.warningthresholdms in zoo.cfg not working
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-2195:
Assignee: Biju Nair
> fsync.warningthresholdms in zoo.cfg not working
> ---
>
> Key: ZOOKEEPER-2195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
>Affects Versions: 3.4.6, 3.5.0
>Reporter: David Fan
>Assignee: Biju Nair
>Priority: Trivial
>
> Config fsync.warningthresholdms in zoo.cfg does not work.
> I find QuorumPeerConfig.parseProperties give fsync.warningthresholdms a
> prefix like "zookeeper.fsync.warningthresholdms". But in class FileTxnLog
> where fsync.warningthresholdms is used, code is
> :Long.getLong("fsync.warningthresholdms", 1000),without prefix "zookeeper.",
> therefore can not get fsync.warningthresholdms's value.
> I wonder the speed of fsync, need this config to see whether the speed is
> good enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2377) zkServer.sh should resolve canonical path from symlinks
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2377: Assignee: Siddhartha > zkServer.sh should resolve canonical path from symlinks > --- > > Key: ZOOKEEPER-2377 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2377 > Project: ZooKeeper > Issue Type: Improvement > Components: scripts >Affects Versions: 3.4.8 > Environment: Centos 6 >Reporter: Siddhartha >Assignee: Siddhartha >Priority: Minor > Attachments: ZOOKEEPER-2377.patch, ZOOKEEPER-2377.patch > > > If zkServer.sh is started from a symlink, it is not able to correctly source > the other scripts because it looks in the wrong path. > Attached patch fixes this by first resolving absolute path to the script. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1100) Killed (or missing) SendThread will cause hanging threads
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1100: Assignee: Camille Fournier > Killed (or missing) SendThread will cause hanging threads > - > > Key: ZOOKEEPER-1100 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1100 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.3.3 > Environment: > http://mail-archives.apache.org/mod_mbox/zookeeper-user/201106.mbox/%3Citpgb6$2mi$1...@dough.gmane.org%3E >Reporter: Gunnar Wagenknecht >Assignee: Camille Fournier > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1100.patch, ZOOKEEPER-1100.patch > > > After investigating an issues with [hanging > threads|http://mail-archives.apache.org/mod_mbox/zookeeper-user/201106.mbox/%3Citpgb6$2mi$1...@dough.gmane.org%3E] > I noticed that any java.lang.Error might silently kill the SendThread. > Without a SendThread any thread that wants to send something will hang > forever. > Currently nobody will recognize a SendThread that died. I think at least a > state should be flipped (or flag should be set) that causes all further send > attempts to fail or to re-spin the connection loop. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1048) addauth command does not work in cli_mt/cli_st
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-1048:
Assignee: allengao
> addauth command does not work in cli_mt/cli_st
> --
>
> Key: ZOOKEEPER-1048
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1048
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
>Affects Versions: 3.3.1
> Environment: SUSE_64
>Reporter: allengao
>Assignee: allengao
> Labels: patch
> Fix For: 3.3.6, 3.4.4, 3.5.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I can not operation a node with ACL by "addauth" when using cli_st. I have
> fixed this bug:
> original：else if (startsWith(line, "addauth ")) {
> char *ptr;
> line += 8;
> ptr = strchr(line, ' ');
> if (ptr) {
> *ptr = '\0';
> ptr++;
> }
> zoo_add_auth(zh, line, ptr, ptr ? strlen(ptr) -1 : 0, NULL, NULL);
> now: zoo_add_auth(zh, line, ptr, ptr ? strlen(ptr) : 0, NULL, NULL);
> strlen(ptr) is just ok.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1163) Memory leak in zk_hashtable.c:do_insert_watcher_object()
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1163: Assignee: Anupam Chanda > Memory leak in zk_hashtable.c:do_insert_watcher_object() > > > Key: ZOOKEEPER-1163 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1163 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.3.3 >Reporter: Anupam Chanda >Assignee: Anupam Chanda > Fix For: 3.3.6, 3.4.4, 3.5.0 > > Attachments: zookeeper-1163.patch > > > zk_hashtable.c:do_insert_watcher_object() line number 193 calls add_to_list > with clone flag set to 1. This leaks memory, since the original watcher > object was already allocated on the heap by activateWatcher() line 330. > I will upload a patch shortly. The fix is to set clone flag to 0 in the call > to add_to_list(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1533) Correct the documentation of the args for the JavaExample doc.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1533: Assignee: Warren Turkal > Correct the documentation of the args for the JavaExample doc. > -- > > Key: ZOOKEEPER-1533 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1533 > Project: ZooKeeper > Issue Type: Bug > Components: documentation >Affects Versions: 3.3.0, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.4.0, 3.4.1, 3.4.2, > 3.4.3, 3.3.5, 3.3.6, 3.4.4, 3.5.0 >Reporter: Warren Turkal >Assignee: Warren Turkal >Priority: Minor > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1533.patch > > > Small doc fix in the JavaExample doc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1128) Recipe wrong for Lock process.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-1128:
Assignee: yynil
> Recipe wrong for Lock process.
> --
>
> Key: ZOOKEEPER-1128
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1128
> Project: ZooKeeper
> Issue Type: Bug
> Components: recipes
>Affects Versions: 3.3.3
>Reporter: yynil
>Assignee: yynil
> Attachments: singulair.html
>
>
> http://zookeeper.apache.org/doc/trunk/recipes.html
> The current recipe for Lock has the wrong process.
> Specifically, for the
> "4. The client calls exists( ) with the watch flag set on the path in the
> lock directory with the next lowest sequence number."
> It shouldn't be the "the next lowest sequence number". It should be the
> "current lowest path".
> If you're gonna use "the next lowest sequence number", you'll never wait for
> the lock possession.
> The following is the test code:
> {code:title=LockTest.java|borderStyle=solid}
> ACL acl = new ACL(Perms.ALL, new Id("10.0.0.0/8", "1"));
> List acls = new ArrayList();
> acls.add(acl);
> String connectStr = "localhost:2181";
> final Semaphore sem = new Semaphore(0);
> ZooKeeper zooKeeper = new ZooKeeper(connectStr, 1000 * 30, new
> Watcher() {
> @Override
> public void process(WatchedEvent event) {
> System.out.println("eventType:" + event.getType());
> System.out.println("keeperState:" + event.getState());
> if (event.getType() == Event.EventType.None) {
> if (event.getState() == Event.KeeperState.SyncConnected) {
> sem.release();
> }
> }
> }
> });
> System.out.println("state:" + zooKeeper.getState());
> System.out.println("Waiting for the state to be connected");
> try {
> sem.acquire();
> } catch (InterruptedException ex) {
> ex.printStackTrace();
> }
> System.out.println("Now state:" + zooKeeper.getState());
> String directory = "/_locknode_";
> Stat stat = zooKeeper.exists(directory, false);
> if (stat == null) {
> zooKeeper.create(directory, new byte[]{},
> ZooDefs.Ids.OPEN_ACL_UNSAFE, CreateMode.PERSISTENT);
> }
> String prefix = directory + "/lock-";
> String path = zooKeeper.create(prefix, new byte[]{},
> ZooDefs.Ids.OPEN_ACL_UNSAFE, CreateMode.EPHEMERAL_SEQUENTIAL);
> System.out.println("Create the path for " + path);
> while (true) {
> List children = zooKeeper.getChildren(directory, false);
> Collections.sort(children);
> System.out.println("The whole lock size is " + children.size());
> String lowestPath = children.get(0);
> DecimalFormat df = new DecimalFormat("00");
> String currentSuffix = lowestPath.substring("lock-".length());
> System.out.println("CurrentSuffix is " + currentSuffix);
> int intIndex = Integer.parseInt(currentSuffix);
> if (path.equals(directory + "/" + lowestPath)) {
> //I've got the lock and release it
> System.out.println("I've got the lock at " + new Date());
> System.out.println("next index is " + intIndex);
> Thread.sleep(1);
> System.out.println("After sleep 3 seconds, I'm gonna release
> the lock");
> zooKeeper.delete(path, -1);
> break;
> }
> final Semaphore wakeupSem = new Semaphore(0);
> stat = zooKeeper.exists(directory + "/" + lowestPath, new
> Watcher() {
> @Override
> public void process(WatchedEvent event) {
> System.out.println("Event is " + event.getType());
> System.out.println("State is " + event.getState());
> if (event.getType() == Event.EventType.NodeDeleted) {
> wakeupSem.release();
> }
> }
> });
> if (stat != null) {
> System.out.println("Waiting for the delete of ");
> wakeupSem.acquire();
> } else {
> System.out.println("Continue to seek");
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1540) ZOOKEEPER-1411 breaks backwards compatibility
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1540: Assignee: Andrew Ferguson > ZOOKEEPER-1411 breaks backwards compatibility > - > > Key: ZOOKEEPER-1540 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1540 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Andrew Ferguson >Assignee: Andrew Ferguson > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1540.patch, ZOOKEEPER-1540.patch > > > There is a one-line bug in ZOOKEEPER-1411 which breaks backwards > compatibility for sites which are using separate configuration files for each > server. The bug is with the handling of the clientPort option. > One line fix to follow shortly. > thanks! > Andrew -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1585) make dist for src/c broken in trunk
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1585: Assignee: Raul Gutierrez Segales > make dist for src/c broken in trunk > --- > > Key: ZOOKEEPER-1585 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1585 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.5.0 >Reporter: Raul Gutierrez Segales >Assignee: Raul Gutierrez Segales > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1585.patch > > > make dist from trunk is failing because of a wrong reference to > src/zookeeper_log.h (which exists in include/). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1731) Unsynchronized access to ServerCnxnFactory.connectionBeans results in deadlock
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-1731:
Assignee: Dave Latham
> Unsynchronized access to ServerCnxnFactory.connectionBeans results in deadlock
> --
>
> Key: ZOOKEEPER-1731
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1731
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Dave Latham
>Assignee: Dave Latham
>Priority: Critical
> Fix For: 3.4.6
>
> Attachments: ZOOKEEPER-1731.patch
>
>
> We had a cluster of 3 peers (running 3.4.3) fail after we took down 1 peer
> briefly for maintenance. A second peer became unresponsive and the leader
> lost quorum. Thread dumps on the second peer showed two threads consistently
> stuck in these states:
> {noformat}
> "QuorumPeer[myid=0]/0.0.0.0:2181" prio=10 tid=0x2aaab8d20800 nid=0x598a
> runnable [0x4335d000]
>java.lang.Thread.State: RUNNABLE
> at java.util.HashMap.put(HashMap.java:405)
> at
> org.apache.zookeeper.server.ServerCnxnFactory.registerConnection(ServerCnxnFactory.java:131)
> at
> org.apache.zookeeper.server.ZooKeeperServer.finishSessionInit(ZooKeeperServer.java:572)
> at
> org.apache.zookeeper.server.quorum.Learner.revalidate(Learner.java:444)
> at
> org.apache.zookeeper.server.quorum.Follower.processPacket(Follower.java:133)
> at
> org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:86)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:740)
> "NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181" daemon prio=10
> tid=0x2aaab84b0800 nid=0x5986 runnable [0x40878000]
>java.lang.Thread.State: RUNNABLE
> at java.util.HashMap.removeEntryForKey(HashMap.java:614)
> at java.util.HashMap.remove(HashMap.java:581)
> at
> org.apache.zookeeper.server.ServerCnxnFactory.unregisterConnection(ServerCnxnFactory.java:120)
> at
> org.apache.zookeeper.server.NIOServerCnxn.close(NIOServerCnxn.java:971)
> - locked <0x00078d8a51f0> (a java.util.HashSet)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.closeSessionWithoutWakeup(NIOServerCnxnFactory.java:307)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.closeSession(NIOServerCnxnFactory.java:294)
> - locked <0x00078d82c750> (a
> org.apache.zookeeper.server.NIOServerCnxnFactory)
> at
> org.apache.zookeeper.server.ZooKeeperServer.processConnectRequest(ZooKeeperServer.java:834)
> at
> org.apache.zookeeper.server.NIOServerCnxn.readConnectRequest(NIOServerCnxn.java:410)
> at
> org.apache.zookeeper.server.NIOServerCnxn.readPayload(NIOServerCnxn.java:200)
> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:236)
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:224)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> It shows both threads concurrently modifying
> ServerCnxnFactory.connectionBeans which is a java.util.HashMap.
> This cluster was serving thousands of clients, which seems to make this
> condition more likely as it appears to occur when one client connects and
> another disconnects at about the same time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1796) Move common code from {Follower, Observer}ZooKeeperServer into LearnerZooKeeperServer
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-1796:
Assignee: Raul Gutierrez Segales
> Move common code from {Follower, Observer}ZooKeeperServer into
> LearnerZooKeeperServer
> -
>
> Key: ZOOKEEPER-1796
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1796
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Raul Gutierrez Segales
>Assignee: Raul Gutierrez Segales
>Priority: Trivial
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1796.patch
>
>
> Since ZOOKEEPER-1552 we are enabling syncProcessor in Observers, so we should
> have a proper shutdown() method there. Since FollowerZooKeeperServer already
> has one, which does the same thing that we need, move that to
> LearnerZooKeeperServer along with some related instance variables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2179) Typo in Watcher.java
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2179: Assignee: Archana T > Typo in Watcher.java > > > Key: ZOOKEEPER-2179 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2179 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.5, 3.5.0 >Reporter: Eunchan Kim >Assignee: Archana T >Priority: Trivial > Fix For: 3.4.7, 3.5.0, 3.6.0 > > Attachments: ZOOKEEPER-2179.patch > > > at zookeeper/src/java/main/org/apache/zookeeper/Watcher.java, > * implement. A ZooKeeper client will get various events from the ZooKeepr > should be fixed to > * implement. A ZooKeeper client will get various events from the ZooKeeper. > (Zookeepr -> Zookeeper) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2096) C client builds with incorrect error codes in VisualStudio 2010+
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-2096: Assignee: Vitaly Stakhovsky > C client builds with incorrect error codes in VisualStudio 2010+ > > > Key: ZOOKEEPER-2096 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2096 > Project: ZooKeeper > Issue Type: Bug > Components: build, c client >Affects Versions: 3.4.6, 3.5.0 > Environment: Windows MSVS 2010+ >Reporter: Vitaly Stakhovsky >Assignee: Vitaly Stakhovsky > Fix For: 3.4.7, 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch, > ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch, > ZOOKEEPER-2096.patch.branch34 > > Original Estimate: 1h > Remaining Estimate: 1h > > It reports: > warning C4005: 'EWOULDBLOCK' : macro redefinition > warning C4005: 'EINPROGRESS' : macro redefinition > In MSVS 2010+, these constants are now in . > What's worse, they have different numeric values. > Possible fix: > In "src/c/include/winconfig.h" : > #if _MSC_VER < 1600 > #define EWOULDBLOCK WSAEWOULDBLOCK > #define EINPROGRESS WSAEINPROGRESS > #endif -- This message was sent by Atlassian JIRA (v6.3.4#6332)
