ZooKeeper-trunk-WinVS2008 - Build # 2449 - Still Failing

2017-04-07 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2449/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by an SCM change
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[EnvInject] - Loading node environment variables.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Building remotely on windows-2012-2 (Windows) in workspace 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
 > git rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Checking out Revision d061f1b5a5eca108e566a68e6f7aa07913c90ac3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d061f1b5a5eca108e566a68e6f7aa07913c90ac3
 > git rev-list d061f1b5a5eca108e566a68e6f7aa07913c90ac3 # timeout=10
No emails were triggered.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[ZooKeeper-trunk-WinVS2008] $ cmd.exe /C 
"F:\jenkins\tools\ant\latest\bin\ant.bat -Dtest.output=yes 
-Dtest.junit.output.format=xml clean compile_jute && exit %%ERRORLEVEL%%"
java.lang.UnsupportedClassVersionError: org/apache/tools/ant/launch/Launcher : 
Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Exception in thread "main" Build step 'Invoke Ant' marked build as failure
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper-trunk-WinVS2008 - Build # 2448 - Still Failing

2017-04-07 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2448/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[EnvInject] - Loading node environment variables.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Building remotely on windows-2012-2 (Windows) in workspace 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
 > git rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Checking out Revision d061f1b5a5eca108e566a68e6f7aa07913c90ac3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d061f1b5a5eca108e566a68e6f7aa07913c90ac3
 > git rev-list d8adc547f9856747905b7d46450f13fa98df147f # timeout=10
No emails were triggered.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[ZooKeeper-trunk-WinVS2008] $ cmd.exe /C 
"F:\jenkins\tools\ant\latest\bin\ant.bat -Dtest.output=yes 
-Dtest.junit.output.format=xml clean compile_jute && exit %%ERRORLEVEL%%"
java.lang.UnsupportedClassVersionError: org/apache/tools/ant/launch/Launcher : 
Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Exception in thread "main" Build step 'Invoke Ant' marked build as failure
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Resolved] (ZOOKEEPER-1609) Improve ZooKeeper performance under mixed workload

2017-04-07 Thread Alexander Shraer (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Shraer resolved ZOOKEEPER-1609.
-
Resolution: Duplicate

I think that this is very similar to what was done with ZOOKEEPER-2024. 

It is still the case that the FinalRequestProcessor only accepts a single write 
request or multiple reads, and this could perhaps be optimized (though not the 
topic of this JIRA), but this would be complex and the benefit is unclear. 

> Improve ZooKeeper performance under mixed workload
> --
>
> Key: ZOOKEEPER-1609
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1609
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.4.3
>Reporter: Thawan Kooburat
>
> ZOOKEEPER-1505 allows 1 write or N reads to pass through the CommitProcessor 
> at any given time. I did performance experiment similar to 
> http://wiki.apache.org/hadoop/ZooKeeper/Performance and found that read 
> throughput drop dramatically when there are write requests. After a bit more 
> investigation, I found that
> the biggest bottleneck is at the request queue entering the CommitProcessor.
> When the CommitProcessor see any write request, it will need to block the 
> entire pipeline and wait until matching commit from the leader. This means 
> that all read requests (including ping request) won't be able to go through. 
> The time spent waiting for commit from the leader far exceed the time spent 
> waiting for 1 write to goes through the CommitProcessor. 
> The current plan is to create multiple request queues at the front of the 
> CommitProcessor. Requests are hashed using sessionId and send to one of the 
> queue. Whenever, the CommitProcessor saw a write request on one of the queue 
> it moves on to process read requests. It will have to unblock the write 
> requests in the same order that it sent to the leader, so it may need to 
> maintain a separate list to keep track of that. 
> The correctness is the same as having more learners in the ensemble. Sessions 
> which are hashed onto a different queue is similar to sessions connecting to 
> a different learners in the ensemble. 
> I am hoping that this will improve read throughput and reduce disconnect rate 
> on an ensemble with large number of clients  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-236) SSL Support for Atomic Broadcast protocol

2017-04-07 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961516#comment-15961516
 ] 

Hadoop QA commented on ZOOKEEPER-236:
-

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 43 new or modified tests.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 findbugs.  The patch does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/521//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/521//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/521//console

This message is automatically generated.

> SSL Support for Atomic Broadcast protocol
> -
>
> Key: ZOOKEEPER-236
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-236
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: quorum, server
>Reporter: Benjamin Reed
>Assignee: Abraham Fine
>Priority: Minor
>
> We should have the ability to use SSL to authenticate and encrypt the traffic 
> between ZooKeeper servers. For the most part this is a very easy change. We 
> would probably only want to support this for TCP based leader elections.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #521

2017-04-07 Thread Apache Jenkins Server 
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/521/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 70.45 MB...]
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/521//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/521//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/521//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] d12b23e5708539dc5f9b1559be1f44487a71488d logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1642:
 exec returned: 1

Total time: 14 minutes 41 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 576.79 KB of artifacts by 38.8% relative to #519
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-236
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.ReconfigDuringLeaderSyncTest.testDuringLeaderSync

Error Message:
zoo.cfg.dynamic.next is not deleted.

Stack Trace:
junit.framework.AssertionFailedError: zoo.cfg.dynamic.next is not deleted.
at 
org.apache.zookeeper.server.quorum.ReconfigDuringLeaderSyncTest.testDuringLeaderSync(ReconfigDuringLeaderSyncTest.java:165)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Commented] (ZOOKEEPER-236) SSL Support for Atomic Broadcast protocol

2017-04-07 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961377#comment-15961377
 ] 

Hadoop QA commented on ZOOKEEPER-236:
-

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 41 new or modified tests.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 findbugs.  The patch does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/520//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/520//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/520//console

This message is automatically generated.

> SSL Support for Atomic Broadcast protocol
> -
>
> Key: ZOOKEEPER-236
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-236
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: quorum, server
>Reporter: Benjamin Reed
>Assignee: Abraham Fine
>Priority: Minor
>
> We should have the ability to use SSL to authenticate and encrypt the traffic 
> between ZooKeeper servers. For the most part this is a very easy change. We 
> would probably only want to support this for TCP based leader elections.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #520

2017-04-07 Thread Apache Jenkins Server 
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/520/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.09 MB...]
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/520//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/520//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/520//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] 5e1a2d7a2ba277ea7c9c0afc0e8d0738a598da50 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1642:
 exec returned: 1

Total time: 22 minutes 2 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 577.56 KB of artifacts by 60.9% relative to #519
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-236
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  org.apache.zookeeper.test.QuorumSSLTest.testRollingUpgrade

Error Message:
Timeout occurred. Please note the time in the report does not reflect the time 
until the timeout.

Stack Trace:
junit.framework.AssertionFailedError: Timeout occurred. Please note the time in 
the report does not reflect the time until the timeout.
at java.lang.Thread.run(Thread.java:745)


FAILED:  org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

Error Message:
KeeperErrorCode = ConnectionLoss for /test

Stack Trace:
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = 
ConnectionLoss for /test
at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1426)
at 
org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.lang.Thread.run(Thread.java:745)

Success: ZOOKEEPER- PreCommit Build #519

2017-04-07 Thread Apache Jenkins Server 
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/519/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 71.46 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 41 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) 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-github-pr-build/519//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/519//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/519//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] 565e1f5d0cb81caa37ab4c37d75c109491640675 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 19 minutes 53 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-236
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-236) SSL Support for Atomic Broadcast protocol

2017-04-07 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961374#comment-15961374
 ] 

Hadoop QA commented on ZOOKEEPER-236:
-

+1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 41 new or modified tests.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 findbugs.  The patch does not introduce any new Findbugs (version 3.0.1) 
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-github-pr-build/519//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/519//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/519//console

This message is automatically generated.

> SSL Support for Atomic Broadcast protocol
> -
>
> Key: ZOOKEEPER-236
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-236
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: quorum, server
>Reporter: Benjamin Reed
>Assignee: Abraham Fine
>Priority: Minor
>
> We should have the ability to use SSL to authenticate and encrypt the traffic 
> between ZooKeeper servers. For the most part this is a very easy change. We 
> would probably only want to support this for TCP based leader elections.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper-trunk-openjdk7 - Build # 1429 - Still Failing

2017-04-07 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1429/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 62.48 MB...]
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-04-07 20:01:58,814 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@617] - Processed session termination for 
sessionid: 0x10374f5f8b3
[junit] 2017-04-07 20:01:58,815 [myid:] - WARN  [New I/O worker 
#9949:NettyServerCnxnFactory$CnxnChannelHandler@142] - Exception caught [id: 
0xe25aeea4, /127.0.0.1:50068 :> /127.0.0.1:14161] EXCEPTION: 
java.nio.channels.ClosedChannelException
[junit] java.nio.channels.ClosedChannelException
[junit] at 
sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
[junit] at 
sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
[junit] at 
org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:201)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:151)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:315)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
[junit] at 
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-04-07 20:01:58,815 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=Connections,name2=127.0.0.1,name3=0x10374f5f8b3]
[junit] 2017-04-07 20:01:58,915 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x10374f5f8b3 closed
[junit] 2017-04-07 20:01:58,916 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 202497
[junit] 2017-04-07 20:01:58,916 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2427
[junit] 2017-04-07 20:01:58,916 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-04-07 20:01:58,916 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-04-07 20:01:58,915 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10374f5f8b3
[junit] 2017-04-07 20:01:58,916 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-04-07 20:01:58,916 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14161
[junit] 2017-04-07 20:01:58,919 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-04-07 20:01:58,919 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-04-07 20:01:58,919 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-04-07 20:01:58,919 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-04-07 20:01:58,920 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-04-07 20:01:58,920 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-04-07 20:01:58,920 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-04-07 20:01:58,920 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-04-07 20:01:58,920 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean

[jira] [Commented] (ZOOKEEPER-2729) Cleanup findbug warnings in branch-3.4: Correctness Warnings

2017-04-07 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961359#comment-15961359
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2729:
---

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/220
  
The javadoc warning from jenkins appears to be unrelated to the patch:
>   [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/src/java/main/org/apache/zookeeper/server/PurgeTxnLog.java:207:
 warning - @return tag has no arguments.

The new findbugs appears to be incorrect as well.


> Cleanup findbug warnings in branch-3.4: Correctness Warnings
> 
>
> Key: ZOOKEEPER-2729
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2729
> Project: ZooKeeper
>  Issue Type: Sub-task
>Affects Versions: 3.4.9
>Reporter: Rakesh R
>Assignee: Abraham Fine
> Fix For: 3.4.11
>
>
> {code}
> (1) INT Bad comparison of nonnegative value with 0 in 
> org.apache.zookeeper.server.quorum.auth.SaslQuorumAuthLearner.send(DataOutputStream,
>  byte[])
> Bug type INT_BAD_COMPARISON_WITH_NONNEGATIVE_VALUE (click for details) 
> In class org.apache.zookeeper.server.quorum.auth.SaslQuorumAuthLearner
> In method 
> org.apache.zookeeper.server.quorum.auth.SaslQuorumAuthLearner.send(DataOutputStream,
>  byte[])
> Value 0
> At SaslQuorumAuthLearner.java:[line 176]
> (2) INT   Bad comparison of nonnegative value with 0 in 
> org.apache.zookeeper.server.quorum.auth.SaslQuorumAuthServer.send(DataOutputStream,
>  byte[], QuorumAuth$Status)
> Bug type INT_BAD_COMPARISON_WITH_NONNEGATIVE_VALUE (click for details) 
> In class org.apache.zookeeper.server.quorum.auth.SaslQuorumAuthServer
> In method 
> org.apache.zookeeper.server.quorum.auth.SaslQuorumAuthServer.send(DataOutputStream,
>  byte[], QuorumAuth$Status)
> Value 0
> At SaslQuorumAuthServer.java:[line 170]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #220: ZOOKEEPER-2729: Cleanup findbug warnings in branch-3.4...

2017-04-07 Thread afine 
Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/220
  
The javadoc warning from jenkins appears to be unrelated to the patch:
>   [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/src/java/main/org/apache/zookeeper/server/PurgeTxnLog.java:207:
 warning - @return tag has no arguments.

The new findbugs appears to be incorrect as well.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2749) Cleanup findbug warnings in branch-3.4: Experimental Warnings

2017-04-07 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961354#comment-15961354
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2749:
---

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/221
  
Looks like the jenkins failure is related to an infra failure


> Cleanup findbug warnings in branch-3.4: Experimental Warnings
> -
>
> Key: ZOOKEEPER-2749
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2749
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Fix For: 3.4.11
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #221: ZOOKEEPER-2749: Cleanup findbug warnings in branch-3.4...

2017-04-07 Thread afine 
Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/221
  
Looks like the jenkins failure is related to an infra failure


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZOOKEEPER-2750) Document SSL Support for Atomic Broadcast protocol

2017-04-07 Thread Abraham Fine (JIRA) 
Abraham Fine created ZOOKEEPER-2750:
---

 Summary: Document SSL Support for Atomic Broadcast protocol
 Key: ZOOKEEPER-2750
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2750
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Abraham Fine
Assignee: Abraham Fine






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

2017-04-07 Thread Michael Han 
Sure, let's extends the vote for another cycle and now the vote will
end on *April
14th 2017, 23:59 UTC+0. *

On Fri, Apr 7, 2017 at 11:57 AM, Raúl Gutiérrez Segalés  wrote:

> +1 -- Is am traveling so I need a few more days to test this in one of our
> dev clusters.
>
>
> -rgs
>
>
> On Apr 7, 2017 2:53 PM, "Flavio Junqueira"  wrote:
>
> > Would it be ok to extend the vote until mid next week?
> >
> > -Flavio
> >
> > > On 03 Apr 2017, at 18:26, Michael Han  wrote:
> > >
> > > Hi all,
> > >
> > > This is the second release candidate (RC1) of 3.5.3-beta, following the
> > > first release candidate (RC0) cut off last week [1]. It fixes incorrect
> > > Implementation-Version information contained in the manifest file of
> the
> > > generated artifacts. There is no code changes, just regenerated and
> > > resigned artifacts.
> > >
> > > The full release notes are available at:
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12310801=12335444
> > >
> > >  Please download, test and vote by April 8th 2017, 23:59 UTC+0.
> 
> > >
> > > Source files:
> > > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/groups/staging/org/
> > > apache/zookeeper/zookeeper/3.5.3-beta/
> > >
> > > The tag to be voted upon:
> > > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > > *
> > >
> > > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > > http://www.apache.org/dist/zookeeper/KEYS
> > >
> > > Should we release this candidate?
> > >
> > > [1]
> > > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> > 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
> > CrHUrw%40mail.gmail.com%3E
> > >
> > > --
> > > Cheers
> > > Michael.
> >
> >
>



-- 
Cheers
Michael.

Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

2017-04-07 Thread Raúl Gutiérrez Segalés 
+1 -- Is am traveling so I need a few more days to test this in one of our
dev clusters.


-rgs


On Apr 7, 2017 2:53 PM, "Flavio Junqueira"  wrote:

> Would it be ok to extend the vote until mid next week?
>
> -Flavio
>
> > On 03 Apr 2017, at 18:26, Michael Han  wrote:
> >
> > Hi all,
> >
> > This is the second release candidate (RC1) of 3.5.3-beta, following the
> > first release candidate (RC0) cut off last week [1]. It fixes incorrect
> > Implementation-Version information contained in the manifest file of the
> > generated artifacts. There is no code changes, just regenerated and
> > resigned artifacts.
> >
> > The full release notes are available at:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12310801=12335444
> >
> >  Please download, test and vote by April 8th 2017, 23:59 UTC+0. 
> >
> > Source files:
> > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/groups/staging/org/
> > apache/zookeeper/zookeeper/3.5.3-beta/
> >
> > The tag to be voted upon:
> > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > *
> >
> > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/zookeeper/KEYS
> >
> > Should we release this candidate?
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
> CrHUrw%40mail.gmail.com%3E
> >
> > --
> > Cheers
> > Michael.
>
>

Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

2017-04-07 Thread Flavio Junqueira 
Would it be ok to extend the vote until mid next week?

-Flavio

> On 03 Apr 2017, at 18:26, Michael Han  wrote:
> 
> Hi all,
> 
> This is the second release candidate (RC1) of 3.5.3-beta, following the
> first release candidate (RC0) cut off last week [1]. It fixes incorrect
> Implementation-Version information contained in the manifest file of the
> generated artifacts. There is no code changes, just regenerated and
> resigned artifacts.
> 
> The full release notes are available at:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310801=12335444
> 
>  Please download, test and vote by April 8th 2017, 23:59 UTC+0. 
> 
> Source files:
> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> 
> Maven staging repo:
> https://repository.apache.org/content/groups/staging/org/
> apache/zookeeper/zookeeper/3.5.3-beta/
> 
> The tag to be voted upon:
> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> *
> 
> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/zookeeper/KEYS
> 
> Should we release this candidate?
> 
> [1]
> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
> 
> -- 
> Cheers
> Michael.

ZooKeeper_branch34_openjdk7 - Build # 1457 - Still Failing

2017-04-07 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1457/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H15 (ubuntu xenial) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 0f83f51644c17aee216031f3848866e182cabb67 
(refs/remotes/origin/branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0f83f51644c17aee216031f3848866e182cabb67
 > git rev-list 0f83f51644c17aee216031f3848866e182cabb67 # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $ 
/home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Dtest.output=yes 
-Dtest.junit.threads=8 -Dtest.junit.output.format=xml -Djavac.target=1.7 clean 
test-core-java
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-1609) Improve ZooKeeper performance under mixed workload

2017-04-07 Thread Atri Sharma (JIRA) 

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960675#comment-15960675
 ] 

Atri Sharma commented on ZOOKEEPER-1609:


Folks, I am planning to work on this. Please let me know if it is relevant and 
is not done yet. [~shralex]

> Improve ZooKeeper performance under mixed workload
> --
>
> Key: ZOOKEEPER-1609
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1609
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.4.3
>Reporter: Thawan Kooburat
>
> ZOOKEEPER-1505 allows 1 write or N reads to pass through the CommitProcessor 
> at any given time. I did performance experiment similar to 
> http://wiki.apache.org/hadoop/ZooKeeper/Performance and found that read 
> throughput drop dramatically when there are write requests. After a bit more 
> investigation, I found that
> the biggest bottleneck is at the request queue entering the CommitProcessor.
> When the CommitProcessor see any write request, it will need to block the 
> entire pipeline and wait until matching commit from the leader. This means 
> that all read requests (including ping request) won't be able to go through. 
> The time spent waiting for commit from the leader far exceed the time spent 
> waiting for 1 write to goes through the CommitProcessor. 
> The current plan is to create multiple request queues at the front of the 
> CommitProcessor. Requests are hashed using sessionId and send to one of the 
> queue. Whenever, the CommitProcessor saw a write request on one of the queue 
> it moves on to process read requests. It will have to unblock the write 
> requests in the same order that it sent to the leader, so it may need to 
> maintain a separate list to keep track of that. 
> The correctness is the same as having more learners in the ensemble. Sessions 
> which are hashed onto a different queue is similar to sessions connecting to 
> a different learners in the ensemble. 
> I am hoping that this will improve read throughput and reduce disconnect rate 
> on an ensemble with large number of clients  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper-trunk-jdk8 - Build # 1007 - Failure

2017-04-07 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/1007/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 62.83 MB...]
[junit] 2017-04-07 11:55:46,988 [myid:127.0.0.1:21994] - WARN  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1235] - Session 
0x102c1afee4b for server 127.0.0.1/127.0.0.1:21994, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-04-07 11:55:47,301 [myid:127.0.0.1:22117] - INFO  
[main-SendThread(127.0.0.1:22117):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22117. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-04-07 11:55:47,302 [myid:127.0.0.1:22117] - WARN  
[main-SendThread(127.0.0.1:22117):ClientCnxn$SendThread@1235] - Session 
0x102c1b3b397 for server 127.0.0.1/127.0.0.1:22117, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-04-07 11:55:47,594 [myid:] - INFO  [ProcessThread(sid:0 
cport:22240)::PrepRequestProcessor@617] - Processed session termination for 
sessionid: 0x102c1b6aa5a
[junit] 2017-04-07 11:55:47,597 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x102c1b6aa5a closed
[junit] 2017-04-07 11:55:47,597 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22240,name1=Connections,name2=127.0.0.1,name3=0x102c1b6aa5a]
[junit] 2017-04-07 11:55:47,597 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 98218
[junit] 2017-04-07 11:55:47,597 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 861
[junit] 2017-04-07 11:55:47,597 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-04-07 11:55:47,598 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-04-07 11:55:47,598 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-04-07 11:55:47,598 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:22240
[junit] 2017-04-07 11:55:47,597 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x102c1b6aa5a
[junit] 2017-04-07 11:55:47,599 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-04-07 11:55:47,599 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-04-07 11:55:47,600 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-04-07 11:55:47,600 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-04-07 11:55:47,600 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-04-07 11:55:47,600 [myid:] - INFO  [ProcessThread(sid:0 
cport:22240)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-04-07 11:55:47,600 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-04-07 11:55:47,600 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-04-07 11:55:47,601 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22240,name1=InMemoryDataTree]
[junit] 2017-04-07 11:55:47,601 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port22240]
[junit] 2017-04-07 11:55:47,601 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 22240
[junit] 2017-04-07 11:55:47,602 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-04-07 11:55:47,611 [myid:] - INFO  [main:ClientBase@583] - 
fdcount after test is: 2540 at start it was 2540
[junit] 2017-04-07 11:55:47,611 [myid:] - INFO

ZooKeeper_branch35_openjdk7 - Build # 484 - Failure

2017-04-07 Thread Apache Jenkins Server 
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/484/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 61.59 MB...]
[junit] 2017-04-07 10:08:00,916 [myid:] - INFO  [main:ZKTestCase$1@73] - 
FAILED testWatcherAutoResetWithLocal
[junit] org.junit.internal.runners.model.MultipleFailureException: There 
were 2 errors:
[junit]   java.lang.AssertionError(Unexpected bean exists! expected:<0> but 
was:<1>)
[junit]   java.lang.AssertionError(expected:<0> but was:<1>)
[junit] at 
org.junit.runners.model.MultipleFailureException.assertEmpty(MultipleFailureException.java:67)
[junit] at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:39)
[junit] at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:53)
[junit] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
[junit] at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
[junit] at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
[junit] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
[junit] at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
[junit] at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
[junit] at 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
[junit] at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
[junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
[junit] at org.junit.runners.Suite.runChild(Suite.java:128)
[junit] at org.junit.runners.Suite.runChild(Suite.java:27)
[junit] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
[junit] at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
[junit] at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
[junit] at 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
[junit] at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
[junit] at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
[junit] at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
[junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
[junit] at 
junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:535)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1182)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1033)
[junit] 2017-04-07 10:08:00,917 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 14, Errors: 0, Skipped: 0, Time elapsed: 
441.071 sec, Thread: 6, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-04-07 10:08:01,016 [myid:127.0.0.1:24810] - INFO  
[main-SendThread(127.0.0.1:24810):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24810. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-04-07 10:08:01,017 [myid:127.0.0.1:24810] - WARN  
[main-SendThread(127.0.0.1:24810):ClientCnxn$SendThread@1235] - Session 
0x10036dbfb2c for server 127.0.0.1/127.0.0.1:24810, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-04-07 10:08:01,091 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-04-07 10:08:01,092 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-04-07 10:08:01,092 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-04-07 10:08:01,092 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-04-07 10:08:01,092 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-04-07 10:08:01,093 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-04-07 10:08:01,093 [myid:] - INFO

Failed: ZOOKEEPER-2742 PreCommit Build #3622

2017-04-07 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2742
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3622/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 800 B...]
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision d061f1b5a5eca108e566a68e6f7aa07913c90ac3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d061f1b5a5eca108e566a68e6f7aa07913c90ac3
 > git rev-list d8adc547f9856747905b7d46450f13fa98df147f # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-Build] $ /bin/bash /tmp/hudson1244145205704558233.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386178
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
No tests ran.