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

[Powell Molleti (JIRA)]

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

Powell Molleti commented on ZOOKEEPER-236:
--

Hi Abe,

Not sure that will work, I think SSL engine will need the the hostname set for 
this to work. Since server cannot know which client will connect it cannot use 
this mechanism I believe. This was meant for client side only. 

thanks
Powell.

> 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)

[jira] [Commented] (ZOOKEEPER-2184) Zookeeper Client should re-resolve hosts when connection attempts fail

[Powell Molleti (JIRA)]

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

Powell Molleti commented on ZOOKEEPER-2184:
---

not sure what the failure above is but the cpp unit tests work for me locally 
for that PR I submitted.
{noformat}
 [exec]  [exec] *** Error in `./zktest-mt': corrupted double-linked 
list: 0x012a5810 ***
 [exec]  [exec] Zookeeper_readOnly::testReadOnly : elapsed 4101 : OK
 [exec]  [exec] OK (74)
 [exec]  [exec] FAIL: zktest-mt
 [exec]  [exec] ==
 [exec]  [exec] 1 of 2 tests failed
 [exec]  [exec] Please report to u...@zookeeper.apache.org
 [exec]  [exec] ==
 [exec]  [exec] make[1]: Leaving directory 
`/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build/test/test-cppunit'
 [exec]  [exec] /bin/bash: line 5:  8114 Aborted (core 
dumped) 
ZKROOT=/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/src/c/../..
 CLASSPATH=$CLASSPATH:$CLOVER_HOME/lib/clover.jar ${dir}$tst
 [exec]  [exec] make[1]: *** [check-TESTS] Error 1
 [exec]  [exec] make: *** [check-am] Error 2
{noformat}



> Zookeeper Client should re-resolve hosts when connection attempts fail
> --
>
> Key: ZOOKEEPER-2184
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.6, 3.5.0
> Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & 
> Kafka
>Reporter: Robert P. Thille
>Assignee: Flavio Junqueira
>  Labels: easyfix, patch
> Fix For: 3.5.4, 3.6.0, 3.4.11
>
> Attachments: ZOOKEEPER-2184.patch
>
>
> Testing in a Docker environment with a single Kafka instance using a single 
> Zookeeper instance. Restarting the Zookeeper container will cause it to 
> receive a new IP address. Kafka will never be able to reconnect to Zookeeper 
> and will hang indefinitely. Updating DNS or /etc/hosts with the new IP 
> address will not help the client to reconnect as the 
> zookeeper/client/StaticHostProvider resolves the connection string hosts at 
> creation time and never re-resolves.
> A solution would be for the client to notice that connection attempts fail 
> and attempt to re-resolve the hostnames in the connectString.



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

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

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2442/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 10.86 KB...]
   [javacc] File "SimpleCharStream.java" does not exist.  Will create one.
   [javacc] Parser generated successfully.

jute:
[javac] Compiling 39 source files to 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\build\classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.7
[javac] 1 warning

compile_jute_uptodate:

compile_jute:
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\java\generated
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\generated
 [java] ../../zookeeper.jute Parsed Successfully
 [java] ../../zookeeper.jute Parsed Successfully
[touch] Creating 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\java\generated\.generated

BUILD SUCCESSFUL
Total time: 7 seconds
[ZooKeeper-trunk-WinVS2008] $ cmd /c call 
C:\Users\jenkins\AppData\Local\Temp\1\hudson3951559843978709059.bat

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>set 
ZOOKEEPER_HOME=f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008 

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>set 
PATH=F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Microsoft SQL Server\130\Tools\Binn\;F:\Program 
Files\CMake\bin;F:\Program Files (x86)\Subversion\bin;C:\Program 
Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\Windows 
Kits\10\Windows Performance Toolkit\;C:\Program Files 
(x86)\nodejs\;C:\Users\jenkins\.dnx\bin;C:\Program Files\Microsoft 
DNX\Dnvm\;C:\Program Files (x86)\Microsoft Emulator Manager\1.0\;C:\Program 
Files (x86)\PuTTY\;F:\Program 
Files\Git\cmd;F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Microsoft SQL Server\130\Tools\Binn\;F:\Program 
Files\CMake\bin;F:\Program Files (x86)\Subversion\bin;C:\Program 
Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\Windows 
Kits\10\Windows Performance Toolkit\;C:\Program Files 
(x86)\nodejs\;C:\Windows\system32\config\systemprofile\.dnx\bin;C:\Program 
Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Microsoft Emulator 
Manager\1.0\;C:\Program Files 
(x86)\PuTTY\;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Microsoft SQL Server\130\Tools\Binn\;F:\Program 
Files\CMake\bin;F:\Program Files (x86)\Subversion\bin;C:\Program 
Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\Windows 
Kits\10\Windows Performance 
Toolkit\;C:\Prog;C:/Windows/Microsoft.NET/Framework/v4.0.30319/ 

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>msbuild 
src/c/zookeeper.sln /p:Configuration=Release 
Microsoft (R) Build Engine version 4.6.1087.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

Building the projects in this solution one at a time. To enable parallel build, 
please add the "/m" switch.
Build started 3/18/2017 5:22:53 AM.
Project 
"f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln"
 on node 1 (default targets).
ValidateSolutionConfiguration:
  Building solution configuration "Release|Win32".
MSBUILD : error MSB3411: Could not load the Visual C++ component "VCBuild.exe". 
If the component is not installed, either 1) install the Microsoft Windows SDK 
for Windows Server 2008 and .NET Framework 3.5, or 2) install Microsoft Visual 
Studio 2008.  
[f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln]
MSBUILD : error MSB3411: Could not load the Visual C++ component "VCBuild.exe". 
If the component is not installed, either 1) install the Microsoft Windows SDK 
for Windows Server 2008 and .NET Framework 3.5, or 2) install Microsoft Visual 
Studio 2008.  
[f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln]
Done Building Project 
"f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln"
 (default targets) -- FAILED.

Build FAILED.

"f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln"
 (default target) (1) ->
(zookeeper target) -> 
  MSBUILD : error MSB3411: Could not load the Visual C++ component 
"VCBuild.exe". If the component is not installed, either 1) install the 
Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5, or 2) 
install 

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

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2443/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 10.87 KB...]
   [javacc] File "SimpleCharStream.java" does not exist.  Will create one.
   [javacc] Parser generated successfully.

jute:
[javac] Compiling 39 source files to 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\build\classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.7
[javac] 1 warning

compile_jute_uptodate:

compile_jute:
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\java\generated
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\generated
 [java] ../../zookeeper.jute Parsed Successfully
 [java] ../../zookeeper.jute Parsed Successfully
[touch] Creating 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\java\generated\.generated

BUILD SUCCESSFUL
Total time: 5 seconds
[ZooKeeper-trunk-WinVS2008] $ cmd /c call 
C:\Users\jenkins\AppData\Local\Temp\1\hudson1239769758567022562.bat

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>set 
ZOOKEEPER_HOME=f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008 

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>set 
PATH=F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Microsoft SQL Server\130\Tools\Binn\;F:\Program 
Files\CMake\bin;F:\Program Files (x86)\Subversion\bin;C:\Program 
Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\Windows 
Kits\10\Windows Performance Toolkit\;C:\Program Files 
(x86)\nodejs\;C:\Users\jenkins\.dnx\bin;C:\Program Files\Microsoft 
DNX\Dnvm\;C:\Program Files (x86)\Microsoft Emulator Manager\1.0\;C:\Program 
Files (x86)\PuTTY\;F:\Program 
Files\Git\cmd;F:\\hudson\\tools\\java\\jdk1.8.0_92-unlimited-security/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Microsoft SQL Server\130\Tools\Binn\;F:\Program 
Files\CMake\bin;F:\Program Files (x86)\Subversion\bin;C:\Program 
Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\Windows 
Kits\10\Windows Performance Toolkit\;C:\Program Files 
(x86)\nodejs\;C:\Windows\system32\config\systemprofile\.dnx\bin;C:\Program 
Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Microsoft Emulator 
Manager\1.0\;C:\Program Files 
(x86)\PuTTY\;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Microsoft SQL Server\130\Tools\Binn\;F:\Program 
Files\CMake\bin;F:\Program Files (x86)\Subversion\bin;C:\Program 
Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files (x86)\Windows 
Kits\10\Windows Performance 
Toolkit\;C:\Prog;C:/Windows/Microsoft.NET/Framework/v4.0.30319/ 

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008>msbuild 
src/c/zookeeper.sln /p:Configuration=Release 
Microsoft (R) Build Engine version 4.6.1087.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

Building the projects in this solution one at a time. To enable parallel build, 
please add the "/m" switch.
Build started 3/18/2017 5:23:06 AM.
Project 
"f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln"
 on node 1 (default targets).
ValidateSolutionConfiguration:
  Building solution configuration "Release|Win32".
MSBUILD : error MSB3411: Could not load the Visual C++ component "VCBuild.exe". 
If the component is not installed, either 1) install the Microsoft Windows SDK 
for Windows Server 2008 and .NET Framework 3.5, or 2) install Microsoft Visual 
Studio 2008.  
[f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln]
MSBUILD : error MSB3411: Could not load the Visual C++ component "VCBuild.exe". 
If the component is not installed, either 1) install the Microsoft Windows SDK 
for Windows Server 2008 and .NET Framework 3.5, or 2) install Microsoft Visual 
Studio 2008.  
[f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln]
Done Building Project 
"f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln"
 (default targets) -- FAILED.

Build FAILED.

"f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008\src\c\zookeeper.sln"
 (default target) (1) ->
(zookeeper target) -> 
  MSBUILD : error MSB3411: Could not load the Visual C++ component 
"VCBuild.exe". If the component is not installed, either 1) install the 
Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5, or 2) 
install 

ZooKeeper_branch34_jdk7 - Build # 1446 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1446/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.53 MB...]
[junit] 2017-03-18 02:41:43,559 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-18 02:41:43,560 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-18 02:41:43,560 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-18 02:41:43,560 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-18 02:41:43,560 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-18 02:41:43,561 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-18 02:41:43,561 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-18 02:41:43,562 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-18 02:41:43,563 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-18 02:41:43,563 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-18 02:41:43,563 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-18 02:41:43,564 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-18 02:41:43,564 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test4016851435409846890.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test4016851435409846890.junit.dir/version-2
[junit] 2017-03-18 02:41:43,569 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-18 02:41:43,569 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-18 02:41:43,570 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:58120
[junit] 2017-03-18 02:41:43,570 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:58120
[junit] 2017-03-18 02:41:43,570 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-18 02:41:43,571 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:58120 (no session established for client)
[junit] 2017-03-18 02:41:43,571 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-18 02:41:43,574 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-18 02:41:43,574 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-18 02:41:43,574 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-18 02:41:43,574 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-18 02:41:43,575 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35676
[junit] 2017-03-18 02:41:43,575 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-18 02:41:43,575 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-18 02:41:43,576 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-18 02:41:43,644 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15adf4ac3f0 closed
[junit] 2017-03-18 02:41:43,644 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-18 02:41:43,644 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15adf4ac3f0
[junit] 2017-03-18 02:41:43,644 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-18 02:41:43,645 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-18 02:41:43,645 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-18 02:41:43,645 

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2722:
--

-1 overall.  GitHub Pull Request  Build
  

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

+1 tests included.  The patch appears to include 7 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/449//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/449//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/449//console

This message is automatically generated.

> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> 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:1423)
>   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)
> {noformat}
> Looks like we should retry before giving up.



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

Failed: ZOOKEEPER- PreCommit Build #449

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/449/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 68.99 MB...]
 [exec] +1 tests included.  The patch appears to include 7 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 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/449//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/449//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/449//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] 898ad012377623246da6a34642a97ce7d684098c 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 17 seconds
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
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2722
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.test.FLETest.testTripleElection

Error Message:
Fewer than a a majority has joined

Stack Trace:
junit.framework.AssertionFailedError: Fewer than a a majority has joined
at org.apache.zookeeper.test.FLETest.runElection(FLETest.java:361)
at 
org.apache.zookeeper.test.FLETest.testTripleElection(FLETest.java:286)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Commented] (ZOOKEEPER-2725) Upgrading to a global session fails with a multiop

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2725:
--

+1 overall.  GitHub Pull Request  Build
  

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

+1 tests included.  The patch appears to include 2 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/448//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/448//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/448//console

This message is automatically generated.

> Upgrading to a global session fails with a multiop
> --
>
> Key: ZOOKEEPER-2725
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2725
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.2
>Reporter: Brian Nixon
>
> On an ensemble with local sessions enabled, when a client with a local 
> session requests the creation of an ephemeral node within a multi-op, the 
> client gets a session expired message.  The same multi-op works if the 
> session is already global. This breaks the client's expectation of seamless 
> promotion from local session to global session server-side. 



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

Success: ZOOKEEPER- PreCommit Build #448

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/448/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 66.87 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 2 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/448//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/448//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/448//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] 13d0474911f015de9180b6558f022cf1c810081d 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 19 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-2725
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

Github pull request clean up

[Liang Han]

FYI I filed INFRA-13690 for cleaning up stable pull requests on github. The
stale pull requests sometimes kick pre-commit Jenkins jobs (which need more
investigation) which is annoying. The initial list of PR that's just closed
by Daniel (from Infra team) is:

1, 23, 35, 49, 60, 73, 75, 107, 139, 197, 198.

-- 
Cheers
Michael.

ZooKeeper-trunk - Build # 3321 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk/3321/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 61.76 MB...]
[junit] 2017-03-17 23:27:51,682 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-03-17 23:27:51,682 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
492.072 sec, Thread: 6, Class: org.apache.zookeeper.test.NettyNettySuiteTest
[junit] 2017-03-17 23:27:51,988 [myid:127.0.0.1:24687] - INFO  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24687. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-17 23:27:51,989 [myid:] - INFO  [New I/O boss 
#98:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:24687
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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-03-17 23:27:51,990 [myid:] - WARN  [New I/O boss 
#98:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0xa6a35258] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:24687
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:24687
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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-03-17 23:27:51,990 [myid:] - INFO  [New I/O boss 
#98:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-03-17 23:27:51,990 [myid:127.0.0.1:24687] - INFO  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x103084217c5 is lost, closing socket connection and attempting 
reconnect

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1338: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1219: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1223: Tests 
failed!

Total time: 11 minutes 30 seconds
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
[WARNINGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording fingerprints
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
Publishing Javadoc
Setting 

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

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

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

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/197


> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



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

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

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

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

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/198


> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



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

[jira] [Commented] (ZOOKEEPER-1936) Server exits when unable to create data directory due to race

[ASF GitHub Bot (JIRA)]

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

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

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/75


> Server exits when unable to create data directory due to race 
> --
>
> Key: ZOOKEEPER-1936
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1936
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6, 3.5.0
>Reporter: Harald Musum
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 3.5.4, 3.6.0
>
> Attachments: ZOOKEEPER-1936.branch-3.4.patch, ZOOKEEPER-1936.patch, 
> ZOOKEEPER-1936.v2.patch, ZOOKEEPER-1936.v3.patch, ZOOKEEPER-1936.v3.patch, 
> ZOOKEEPER-1936.v4.patch, ZOOKEEPER-1936.v5.patch
>
>
> We sometime see issues with ZooKeeper server not starting and seeing this 
> error in the log:
> [2014-05-27 09:29:48.248] ERROR   : -   
> .org.apache.zookeeper.server.ZooKeeperServerMainUnexpected exception,
> exiting abnormally\nexception=\njava.io.IOException: Unable to create data
> directory /home/y/var/zookeeper/version-2\n\tat
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:85)\n\tat
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:103)\n\tat
> org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:86)\n\tat
> org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:52)\n\tat
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)\n\tat
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)\n\t
> [...]
> Stack trace from JVM gives this:
> "PurgeTask" daemon prio=10 tid=0x0201d000 nid=0x1727 runnable
> [0x7f55d7dc7000]
>java.lang.Thread.State: RUNNABLE
> at java.io.UnixFileSystem.createDirectory(Native Method)
> at java.io.File.mkdir(File.java:1310)
> at java.io.File.mkdirs(File.java:1337)
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:84)
> at org.apache.zookeeper.server.PurgeTxnLog.purge(PurgeTxnLog.java:68)
> at
> org.apache.zookeeper.server.DatadirCleanupManager$PurgeTask.run(DatadirCleanupManager.java:140)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> "zookeeper server" prio=10 tid=0x027df800 nid=0x1715 runnable
> [0x7f55d7ed8000]
>java.lang.Thread.State: RUNNABLE
> at java.io.UnixFileSystem.createDirectory(Native Method)
> at java.io.File.mkdir(File.java:1310)
> at java.io.File.mkdirs(File.java:1337)
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:84)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:103)
> 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)
> [...]
> So it seems that when autopurge is used (as it is in our case), it might 
> happen at the same time as starting the server itself. In FileTxnSnapLog() it 
> will check if the directory exists and create it if not. These two tasks do 
> this at the same time, and mkdir fails and server exits the JVM.



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

[GitHub] zookeeper pull request #197: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introd...

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/197


---
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.
---

[GitHub] zookeeper pull request #139: EndOfStreamException: Unable to read additional...

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/139


---
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.
---

[GitHub] zookeeper pull request #198: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introd...

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/198


---
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.
---

[GitHub] zookeeper pull request #107: Branch 3.3

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/107


---
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.
---

[GitHub] zookeeper pull request #73: practise git

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/73


---
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.
---

[GitHub] zookeeper pull request #75: https://issues.apache.org/jira/browse/ZOOKEEPER-...

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/75


---
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.
---

[GitHub] zookeeper pull request #49: Zookeeper 1045

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/49


---
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.
---

[GitHub] zookeeper pull request #60: Branch 3.1

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/60


---
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.
---

[GitHub] zookeeper pull request #23: Branch 3.5 add copy directory from source to des...

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/23


---
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.
---

[GitHub] zookeeper pull request #35: Branch 3.5

[Humbedooh]

Github user Humbedooh closed the pull request at:

https://github.com/apache/zookeeper/pull/35


---
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-169) Content needed: "Connecting to ZooKeeper"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ZOOKEEPER-169:
--

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/189#discussion_r106760299
  
--- Diff: src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml 
---
@@ -1714,7 +1714,115 @@ public abstract class ServerAuthenticationProvider 
implements AuthenticationProv
 
   Connecting to ZooKeeper
 
-  
+  Before we begin, you will have to set up a running Zookeeper 
server so that we can start developing the client. For C client bindings, we 
will be using the multithreaded library(zookeeper_mt) with a simple example 
written in C. To establish a connection with Zookeeper server, we make use of C 
API - zookeeper_init with the following signature:
+
+  int 
zookeeper_init(const 
char *host, watcher_fn fn, int 
recv_timeout, const clientid_t *clientid, 
void *context, int 
flags);
+
+  
+
+  *host
+
+  Connection string to zookeeper server in the format of 
host:port. If there are multiple servers, use comma as separator after 
specifying the host:port pairs. Eg: 
"127.0.0.1:2181,127.0.0.1:3001,127.0.0.1:3002"
+
+
+
+
+  fn
+  
+  Watcher function to process events when a notification 
is triggered.
+  
+
+
+
+  recv_timeout
+  
+  Session expiration time in milliseconds.
+  
+
+
+
+  *clientid
+  
+  We can specify 0 for a new session. If a session has 
already establish previously, we could provide that client ID and it would 
reconnect to that previous session.
+  
+
+
+
+  *context
+  
+  Context object that can be associated with the 
zkhandle_t handler. If it is not used, we can set it to 0.
+  
+
+
+
+  flags
+  
+  In an initiation, we can leave it for 0.
+  
+
+  
+
+  We will demonstrate client that outputs "Connected to 
Zookeeper" after successful connection or an error message otherwise. Let's 
call the following code zkClient.cc :
+  
+#include stdio.h>
+#include zookeeper/zookeeper.h>
+#include errno.h>
+using namespace std;
+
+// Keeping track of the connection state
+static int connected = 0;
+static int expired   = 0;
+
+// *zkHandler handles the connection with Zookeeper
+static zhandle_t *zkHandler;
+
+// watcher function would process events
+void watcher(zhandle_t *zkH, int type, int state, const char *path, void 
*watcherCtx)
+{
+if (type == ZOO_SESSION_EVENT) {
+
+// state refers to states of zookeeper connection.
+// To keep it simple, we would demonstrate these 3: 
ZOO_EXPIRED_SESSION_STATE, ZOO_CONNECTED_STATE, ZOO_NOTCONNECTED_STATE
+// If you are using ACL, you should be aware of an authentication 
failure state - ZOO_AUTH_FAILED_STATE
+if (state == ZOO_CONNECTED_STATE) {
+connected = 1;
+} else if (state == ZOO_NOTCONNECTED_STATE ) {
+connected = 0;
+} else if (state == ZOO_EXPIRED_SESSION_STATE) {
+expired = 1;
+connected = 0;
+zookeeper_close(zkH);
+}
+}
+}
+
+int main(){
+zoo_set_debug_level(ZOO_LOG_LEVEL_DEBUG);
+
+// zookeeper_init returns the handler upon a successful connection, 
null otherwise
+zkHandler = zookeeper_init("localhost:2181", watcher, 1, 0, 0, 0);
+
+if (!zkHandler) {
+return errno;
+}else{
+printf("Connection established with Zookeeper. \n");
+}
+
+// Close Zookeeper connection
+zookeeper_close(zkHandler);
+
+return 0;
+}
+  
+
+  Compile the code with the multithreaded library mentioned 
before.
+   g++ -Iinclude/ zkClient.cpp -lzookeeper_mt -o 
Client
--- End diff --

I would file a JIRA for that so we can make the best decision there.


> Content needed: "Connecting to ZooKeeper"
> -
>
> Key: ZOOKEEPER-169
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-169
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Robbie Scott
>   

[GitHub] zookeeper pull request #189: ZOOKEEPER-169: Content needed: "Connecting to Z...

[afine]

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/189#discussion_r106760299
  
--- Diff: src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml 
---
@@ -1714,7 +1714,115 @@ public abstract class ServerAuthenticationProvider 
implements AuthenticationProv
 
   Connecting to ZooKeeper
 
-  
+  Before we begin, you will have to set up a running Zookeeper 
server so that we can start developing the client. For C client bindings, we 
will be using the multithreaded library(zookeeper_mt) with a simple example 
written in C. To establish a connection with Zookeeper server, we make use of C 
API - zookeeper_init with the following signature:
+
+  int 
zookeeper_init(const 
char *host, watcher_fn fn, int 
recv_timeout, const clientid_t *clientid, 
void *context, int 
flags);
+
+  
+
+  *host
+
+  Connection string to zookeeper server in the format of 
host:port. If there are multiple servers, use comma as separator after 
specifying the host:port pairs. Eg: 
"127.0.0.1:2181,127.0.0.1:3001,127.0.0.1:3002"
+
+
+
+
+  fn
+  
+  Watcher function to process events when a notification 
is triggered.
+  
+
+
+
+  recv_timeout
+  
+  Session expiration time in milliseconds.
+  
+
+
+
+  *clientid
+  
+  We can specify 0 for a new session. If a session has 
already establish previously, we could provide that client ID and it would 
reconnect to that previous session.
+  
+
+
+
+  *context
+  
+  Context object that can be associated with the 
zkhandle_t handler. If it is not used, we can set it to 0.
+  
+
+
+
+  flags
+  
+  In an initiation, we can leave it for 0.
+  
+
+  
+
+  We will demonstrate client that outputs "Connected to 
Zookeeper" after successful connection or an error message otherwise. Let's 
call the following code zkClient.cc :
+  
+#include stdio.h>
+#include zookeeper/zookeeper.h>
+#include errno.h>
+using namespace std;
+
+// Keeping track of the connection state
+static int connected = 0;
+static int expired   = 0;
+
+// *zkHandler handles the connection with Zookeeper
+static zhandle_t *zkHandler;
+
+// watcher function would process events
+void watcher(zhandle_t *zkH, int type, int state, const char *path, void 
*watcherCtx)
+{
+if (type == ZOO_SESSION_EVENT) {
+
+// state refers to states of zookeeper connection.
+// To keep it simple, we would demonstrate these 3: 
ZOO_EXPIRED_SESSION_STATE, ZOO_CONNECTED_STATE, ZOO_NOTCONNECTED_STATE
+// If you are using ACL, you should be aware of an authentication 
failure state - ZOO_AUTH_FAILED_STATE
+if (state == ZOO_CONNECTED_STATE) {
+connected = 1;
+} else if (state == ZOO_NOTCONNECTED_STATE ) {
+connected = 0;
+} else if (state == ZOO_EXPIRED_SESSION_STATE) {
+expired = 1;
+connected = 0;
+zookeeper_close(zkH);
+}
+}
+}
+
+int main(){
+zoo_set_debug_level(ZOO_LOG_LEVEL_DEBUG);
+
+// zookeeper_init returns the handler upon a successful connection, 
null otherwise
+zkHandler = zookeeper_init("localhost:2181", watcher, 1, 0, 0, 0);
+
+if (!zkHandler) {
+return errno;
+}else{
+printf("Connection established with Zookeeper. \n");
+}
+
+// Close Zookeeper connection
+zookeeper_close(zkHandler);
+
+return 0;
+}
+  
+
+  Compile the code with the multithreaded library mentioned 
before.
+   g++ -Iinclude/ zkClient.cpp -lzookeeper_mt -o 
Client
--- End diff --

I would file a JIRA for that so we can make the best decision there.


---
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.
---

ZooKeeper_branch34_jdk8 - Build # 923 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/923/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.12 MB...]
[junit] 2017-03-17 22:57:30,107 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-17 22:57:30,107 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-17 22:57:30,107 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-17 22:57:30,107 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-17 22:57:30,107 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-17 22:57:30,107 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-17 22:57:30,108 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-17 22:57:30,108 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-17 22:57:30,110 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-17 22:57:30,110 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-17 22:57:30,111 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-17 22:57:30,111 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-17 22:57:30,111 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test2230945597519880639.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test2230945597519880639.junit.dir/version-2
[junit] 2017-03-17 22:57:30,115 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 22:57:30,115 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-17 22:57:30,116 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:39248
[junit] 2017-03-17 22:57:30,116 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:39248
[junit] 2017-03-17 22:57:30,117 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-17 22:57:30,118 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:39248 (no session established for client)
[junit] 2017-03-17 22:57:30,118 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-17 22:57:30,120 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-17 22:57:30,120 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-17 22:57:30,120 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-17 22:57:30,120 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-17 22:57:30,121 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35519
[junit] 2017-03-17 22:57:30,121 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-17 22:57:30,121 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-17 22:57:30,121 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-17 22:57:30,190 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ade7d7b54 closed
[junit] 2017-03-17 22:57:30,190 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ade7d7b54
[junit] 2017-03-17 22:57:30,191 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-17 22:57:30,191 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-17 22:57:30,192 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-17 22:57:30,192 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 22:57:30,192 

[jira] [Commented] (ZOOKEEPER-2725) Upgrading to a global session fails with a multiop

[ASF GitHub Bot (JIRA)]

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

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

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/195#discussion_r106757640
  
--- Diff: 
src/java/test/org/apache/zookeeper/server/MultiOpSessionUpgradeTest.java ---
@@ -0,0 +1,87 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.zookeeper.server;
+
+import org.apache.zookeeper.CreateMode;
+import org.apache.zookeeper.KeeperException;
+import org.apache.zookeeper.Op;
+import org.apache.zookeeper.OpResult;
+import org.apache.zookeeper.ZooDefs;
+import org.apache.zookeeper.ZooKeeper;
+import org.apache.zookeeper.test.ClientBase;
+import org.apache.zookeeper.test.QuorumBase;
+import org.junit.Assert;
+import org.junit.Test;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.List;
+
+public class MultiOpSessionUpgradeTest extends QuorumBase {
+protected static final Logger LOG = 
LoggerFactory.getLogger(MultiOpSessionUpgradeTest.class);
+
+@Override
+public void setUp() throws Exception {
+localSessionsEnabled = true;
+localSessionsUpgradingEnabled = true;
+super.setUp();
+}
+
+@Test
+public void ephemeralCreateMultiOpTest() throws KeeperException, 
InterruptedException, IOException {
+final ZooKeeper zk = createClient();
+waitForClient(zk, ZooKeeper.States.CONNECTED);
--- End diff --

Not sure we need this. I don't think we need to do this in other tests.


> Upgrading to a global session fails with a multiop
> --
>
> Key: ZOOKEEPER-2725
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2725
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.2
>Reporter: Brian Nixon
>
> On an ensemble with local sessions enabled, when a client with a local 
> session requests the creation of an ephemeral node within a multi-op, the 
> client gets a session expired message.  The same multi-op works if the 
> session is already global. This breaks the client's expectation of seamless 
> promotion from local session to global session server-side. 



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

[GitHub] zookeeper pull request #195: ZOOKEEPER-2725: Promote local session to global...

[afine]

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/195#discussion_r106759077
  
--- Diff: 
src/java/test/org/apache/zookeeper/server/MultiOpSessionUpgradeTest.java ---
@@ -0,0 +1,87 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.zookeeper.server;
+
+import org.apache.zookeeper.CreateMode;
+import org.apache.zookeeper.KeeperException;
+import org.apache.zookeeper.Op;
+import org.apache.zookeeper.OpResult;
+import org.apache.zookeeper.ZooDefs;
+import org.apache.zookeeper.ZooKeeper;
+import org.apache.zookeeper.test.ClientBase;
+import org.apache.zookeeper.test.QuorumBase;
+import org.junit.Assert;
+import org.junit.Test;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.List;
+
+public class MultiOpSessionUpgradeTest extends QuorumBase {
--- End diff --

Would it be possible to test `public Request checkUpgradeSession(Request 
request)` directly in addition to this integration style test?


---
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-2725) Upgrading to a global session fails with a multiop

[ASF GitHub Bot (JIRA)]

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

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

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/195#discussion_r106759077
  
--- Diff: 
src/java/test/org/apache/zookeeper/server/MultiOpSessionUpgradeTest.java ---
@@ -0,0 +1,87 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.zookeeper.server;
+
+import org.apache.zookeeper.CreateMode;
+import org.apache.zookeeper.KeeperException;
+import org.apache.zookeeper.Op;
+import org.apache.zookeeper.OpResult;
+import org.apache.zookeeper.ZooDefs;
+import org.apache.zookeeper.ZooKeeper;
+import org.apache.zookeeper.test.ClientBase;
+import org.apache.zookeeper.test.QuorumBase;
+import org.junit.Assert;
+import org.junit.Test;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.List;
+
+public class MultiOpSessionUpgradeTest extends QuorumBase {
--- End diff --

Would it be possible to test `public Request checkUpgradeSession(Request 
request)` directly in addition to this integration style test?


> Upgrading to a global session fails with a multiop
> --
>
> Key: ZOOKEEPER-2725
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2725
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.2
>Reporter: Brian Nixon
>
> On an ensemble with local sessions enabled, when a client with a local 
> session requests the creation of an ephemeral node within a multi-op, the 
> client gets a session expired message.  The same multi-op works if the 
> session is already global. This breaks the client's expectation of seamless 
> promotion from local session to global session server-side. 



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

[jira] [Commented] (ZOOKEEPER-2725) Upgrading to a global session fails with a multiop

[ASF GitHub Bot (JIRA)]

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

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

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/195#discussion_r106757751
  
--- Diff: 
src/java/test/org/apache/zookeeper/server/MultiOpSessionUpgradeTest.java ---
@@ -0,0 +1,87 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.zookeeper.server;
+
+import org.apache.zookeeper.CreateMode;
+import org.apache.zookeeper.KeeperException;
+import org.apache.zookeeper.Op;
+import org.apache.zookeeper.OpResult;
+import org.apache.zookeeper.ZooDefs;
+import org.apache.zookeeper.ZooKeeper;
+import org.apache.zookeeper.test.ClientBase;
+import org.apache.zookeeper.test.QuorumBase;
+import org.junit.Assert;
+import org.junit.Test;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.List;
+
+public class MultiOpSessionUpgradeTest extends QuorumBase {
+protected static final Logger LOG = 
LoggerFactory.getLogger(MultiOpSessionUpgradeTest.class);
+
+@Override
+public void setUp() throws Exception {
+localSessionsEnabled = true;
+localSessionsUpgradingEnabled = true;
+super.setUp();
+}
+
+@Test
+public void ephemeralCreateMultiOpTest() throws KeeperException, 
InterruptedException, IOException {
+final ZooKeeper zk = createClient();
+waitForClient(zk, ZooKeeper.States.CONNECTED);
+
+String data = "test";
+String path = "/ephemeralcreatemultiop";
+zk.create(path, new byte[0], ZooDefs.Ids.OPEN_ACL_UNSAFE, 
CreateMode.PERSISTENT);
+
+List multi = null;
+LOG.info("RUNNING MULTI-OP");
--- End diff --

nit: not sure we need all of this logging


> Upgrading to a global session fails with a multiop
> --
>
> Key: ZOOKEEPER-2725
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2725
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.2
>Reporter: Brian Nixon
>
> On an ensemble with local sessions enabled, when a client with a local 
> session requests the creation of an ephemeral node within a multi-op, the 
> client gets a session expired message.  The same multi-op works if the 
> session is already global. This breaks the client's expectation of seamless 
> promotion from local session to global session server-side. 



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

[GitHub] zookeeper pull request #195: ZOOKEEPER-2725: Promote local session to global...

[afine]

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/195#discussion_r106757640
  
--- Diff: 
src/java/test/org/apache/zookeeper/server/MultiOpSessionUpgradeTest.java ---
@@ -0,0 +1,87 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.zookeeper.server;
+
+import org.apache.zookeeper.CreateMode;
+import org.apache.zookeeper.KeeperException;
+import org.apache.zookeeper.Op;
+import org.apache.zookeeper.OpResult;
+import org.apache.zookeeper.ZooDefs;
+import org.apache.zookeeper.ZooKeeper;
+import org.apache.zookeeper.test.ClientBase;
+import org.apache.zookeeper.test.QuorumBase;
+import org.junit.Assert;
+import org.junit.Test;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.List;
+
+public class MultiOpSessionUpgradeTest extends QuorumBase {
+protected static final Logger LOG = 
LoggerFactory.getLogger(MultiOpSessionUpgradeTest.class);
+
+@Override
+public void setUp() throws Exception {
+localSessionsEnabled = true;
+localSessionsUpgradingEnabled = true;
+super.setUp();
+}
+
+@Test
+public void ephemeralCreateMultiOpTest() throws KeeperException, 
InterruptedException, IOException {
+final ZooKeeper zk = createClient();
+waitForClient(zk, ZooKeeper.States.CONNECTED);
--- End diff --

Not sure we need this. I don't think we need to do this in other tests.


---
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.
---

[GitHub] zookeeper pull request #195: ZOOKEEPER-2725: Promote local session to global...

[afine]

Github user afine commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/195#discussion_r106757751
  
--- Diff: 
src/java/test/org/apache/zookeeper/server/MultiOpSessionUpgradeTest.java ---
@@ -0,0 +1,87 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.zookeeper.server;
+
+import org.apache.zookeeper.CreateMode;
+import org.apache.zookeeper.KeeperException;
+import org.apache.zookeeper.Op;
+import org.apache.zookeeper.OpResult;
+import org.apache.zookeeper.ZooDefs;
+import org.apache.zookeeper.ZooKeeper;
+import org.apache.zookeeper.test.ClientBase;
+import org.apache.zookeeper.test.QuorumBase;
+import org.junit.Assert;
+import org.junit.Test;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.List;
+
+public class MultiOpSessionUpgradeTest extends QuorumBase {
+protected static final Logger LOG = 
LoggerFactory.getLogger(MultiOpSessionUpgradeTest.class);
+
+@Override
+public void setUp() throws Exception {
+localSessionsEnabled = true;
+localSessionsUpgradingEnabled = true;
+super.setUp();
+}
+
+@Test
+public void ephemeralCreateMultiOpTest() throws KeeperException, 
InterruptedException, IOException {
+final ZooKeeper zk = createClient();
+waitForClient(zk, ZooKeeper.States.CONNECTED);
+
+String data = "test";
+String path = "/ephemeralcreatemultiop";
+zk.create(path, new byte[0], ZooDefs.Ids.OPEN_ACL_UNSAFE, 
CreateMode.PERSISTENT);
+
+List multi = null;
+LOG.info("RUNNING MULTI-OP");
--- End diff --

nit: not sure we need all of this logging


---
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] [Comment Edited] (ZOOKEEPER-236) SSL Support for Atomic Broadcast protocol

[Abraham Fine (JIRA)]

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

Abraham Fine edited comment on ZOOKEEPER-236 at 3/17/17 10:20 PM:
--

Hi [~geek101]-

bq. Regarding host verification one other way to go is to follow this: 
X509ExtendedTrustManager mentions about where to plugin host verification , it 
specifically quotes:
Let me know if this is what you had in mind. We do not need to subclass 
`X509ExtendedTrustManager` ourselves to get this to work, since the 
`X509TrustManagerImpl` object generated by the PKIX trustmanager factory (and 
x509 as well I think) extends `X509ExtendedTrustManager` already.  If endpoint 
verification is set on the sslParameters of the sslSocket we get endpoint 
verification for free in `X509ExtendedTrustManager`. The issue is that we are 
limited to the built in implementations of endpoint verification but I think 
the "https" algorithm is sufficient for our use case.

I implemented this here: 
https://github.com/apache/zookeeper/pull/184/commits/bebe09660f652f243e746905460ecbdffe2d155e


was (Author: abrahamfine):
Hi [~geek101]-

bq. Regarding host verification one other way to go is to follow this: 
X509ExtendedTrustManager mentions about where to plugin host verification , it 
specifically quotes:
Let me know if this is what you had in mind. We do not need to subclass 
`X509ExtendedTrustManager` ourselves to get this to work, since the 
`X509TrustManagerImpl` object generated by the PKIX trustmanager factory (and 
x509 as well I think) extends `X509ExtendedTrustManager` already.  If endpoint 
verification is set on the sslParameters of the sslSocket we get endpoint 
verification for free in `X509ExtendedTrustManager`. The issue is that we are 
limited to the built in implementations of endpoint verification but I think 
the "https" algorithm is sufficient for our use case.  

> 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)

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

[Abraham Fine (JIRA)]

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

Abraham Fine commented on ZOOKEEPER-236:


Hi [~geek101]-

bq. Regarding host verification one other way to go is to follow this: 
X509ExtendedTrustManager mentions about where to plugin host verification , it 
specifically quotes:
Let me know if this is what you had in mind. We do not need to subclass 
`X509ExtendedTrustManager` ourselves to get this to work, since the 
`X509TrustManagerImpl` object generated by the PKIX trustmanager factory (and 
x509 as well I think) extends `X509ExtendedTrustManager` already.  If endpoint 
verification is set on the sslParameters of the sslSocket we get endpoint 
verification for free in `X509ExtendedTrustManager`. The issue is that we are 
limited to the built in implementations of endpoint verification but I think 
the "https" algorithm is sufficient for our use case.  

> 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 #446

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/446/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3.15 KB...]
 [exec]   % Total% Received % Xferd  Average Speed   TimeTime 
Time  CurrentPull request id: 184
 [exec]  Dload  Upload   Total   Spent
Left  Speed
 [exec] 
 [exec] 
 [exec] Pull request title: ZOOKEEPER-236: SSL Support for Atomic Broadcast 
protocol [DO NOT MERGE]
 [exec] Defect number: ZOOKEEPER-236
 [exec] - Parsed args, going to checkout -
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Testing patch for pull request 184.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec]   0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0100   1410   1410 0358  0 --:--:-- --:--:-- 
--:--:--   358
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec]  Pre-build trunk to verify trunk stability and javac warnings
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] /home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant  
-Djavac.args=-Xlint -Xmaxwarns 1000 
-Djava5.home=/home/jenkins/tools/java5/latest 
-Dforrest.home=/home/jenkins/tools/forrest/latest -DZookeeperPatchProcess= 
clean tar > 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess/trunkJavacWarnings.txt
 2>&1
 [exec] Trunk compilation is broken?
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec]   0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0  0 00 412440 0  40271  0 --:--:--  0:00:01 
--:--:--  244kmv: 
'/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: 18 seconds
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?
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) 
##
No tests ran.

Failed: ZOOKEEPER- PreCommit Build #447

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/447/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3.12 KB...]
 [exec] Pull request id: 184
 [exec] Pull request title: ZOOKEEPER-236: SSL Support for Atomic Broadcast 
protocol [DO NOT MERGE]
 [exec] Defect number: ZOOKEEPER-236  % Total% Received % Xferd  
Average Speed   TimeTime Time  Current
 [exec] 
 [exec] - Parsed args, going to checkout -
 [exec] 
 [exec] 
 [exec]  Dload  Upload   Total   Spent
Left  Speed
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Testing patch for pull request 184.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec]   0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0100   1410   1410 0341  0 --:--:-- --:--:-- 
--:--:--   342
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec]  Pre-build trunk to verify trunk stability and javac warnings
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] /home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant  
-Djavac.args=-Xlint -Xmaxwarns 1000 
-Djava5.home=/home/jenkins/tools/java5/latest 
-Dforrest.home=/home/jenkins/tools/forrest/latest -DZookeeperPatchProcess= 
clean tar > 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess/trunkJavacWarnings.txt
 2>&1
 [exec] Trunk compilation is broken?
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec]   0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0  0 00 412440 0  41317  0 --:--:-- --:--:-- 
--:--:-- 88128mv: 
'/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: 25 seconds
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?
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) 
##
No tests ran.

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

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1405/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 64.47 MB...]
[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-03-17 20:02:14,739 [myid:] - INFO  [ProcessThread(sid:0 
cport:16854)::PrepRequestProcessor@617] - Processed session termination for 
sessionid: 0x10308d3febb
[junit] 2017-03-17 20:02:14,740 [myid:] - WARN  [New I/O worker 
#9949:NettyServerCnxnFactory$CnxnChannelHandler@142] - Exception caught [id: 
0x8dcedaa7, /127.0.0.1:45808 :> /127.0.0.1:16854] 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-03-17 20:02:14,741 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port16854,name1=Connections,name2=127.0.0.1,name3=0x10308d3febb]
[junit] 2017-03-17 20:02:14,840 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x10308d3febb closed
[junit] 2017-03-17 20:02:14,841 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10308d3febb
[junit] 2017-03-17 20:02:14,841 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 223956
[junit] 2017-03-17 20:02:14,841 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2427
[junit] 2017-03-17 20:02:14,841 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-17 20:02:14,841 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-03-17 20:02:14,841 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-03-17 20:02:14,841 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:16854
[junit] 2017-03-17 20:02:14,844 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-03-17 20:02:14,845 [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-03-17 20:02:14,845 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-17 20:02:14,845 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-03-17 20:02:14,845 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-17 20:02:14,845 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-17 20:02:14,845 [myid:] - INFO  [ProcessThread(sid:0 
cport:16854)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-03-17 20:02:14,848 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-17 20:02:14,849 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port16854,name1=InMemoryDataTree]
[junit] 2017-03-17 

[jira] [Commented] (ZOOKEEPER-2659) Use log4j2 as a logging framework as log4j 1.X is now deprecated

[ASF GitHub Bot (JIRA)]

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

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

Github user jvz commented on the issue:

https://github.com/apache/zookeeper/pull/148
  
I'm still interested in it, though I'm not a Zookeeper committer, so I 
can't do anything about it.


> Use log4j2 as a logging framework as log4j 1.X is now deprecated
> 
>
> Key: ZOOKEEPER-2659
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2659
> Project: ZooKeeper
>  Issue Type: Wish
>Reporter: Pushkar Raste
>Assignee: Pushkar Raste
>Priority: Minor
> Attachments: zk_log4j2_migration.patch
>
>
> Zookeeper currently uses {{log4j 1.X}} as the default logging framework. 
> {{log4j 1.X}} is now deprecated http://logging.apache.org/log4j/1.2/
> This ticket is to track efforts to move zookeeper to {{log4j2}}



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

[GitHub] zookeeper issue #148: ZOOKEEPER-2659 Log4j 2 migration

[jvz]

Github user jvz commented on the issue:

https://github.com/apache/zookeeper/pull/148
  
I'm still interested in it, though I'm not a Zookeeper committer, so I 
can't do anything about it.


---
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] [Resolved] (ZOOKEEPER-2659) Use log4j2 as a logging framework as log4j 1.X is now deprecated

[Pushkar Raste (JIRA)]

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

Pushkar Raste resolved ZOOKEEPER-2659.
--
Resolution: Won't Do

> Use log4j2 as a logging framework as log4j 1.X is now deprecated
> 
>
> Key: ZOOKEEPER-2659
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2659
> Project: ZooKeeper
>  Issue Type: Wish
>Reporter: Pushkar Raste
>Assignee: Pushkar Raste
>Priority: Minor
> Attachments: zk_log4j2_migration.patch
>
>
> Zookeeper currently uses {{log4j 1.X}} as the default logging framework. 
> {{log4j 1.X}} is now deprecated http://logging.apache.org/log4j/1.2/
> This ticket is to track efforts to move zookeeper to {{log4j2}}



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

[jira] [Commented] (ZOOKEEPER-2659) Use log4j2 as a logging framework as log4j 1.X is now deprecated

[ASF GitHub Bot (JIRA)]

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

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

Github user praste commented on the issue:

https://github.com/apache/zookeeper/pull/148
  
Looks like no one is really interested in this. 


> Use log4j2 as a logging framework as log4j 1.X is now deprecated
> 
>
> Key: ZOOKEEPER-2659
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2659
> Project: ZooKeeper
>  Issue Type: Wish
>Reporter: Pushkar Raste
>Assignee: Pushkar Raste
>Priority: Minor
> Attachments: zk_log4j2_migration.patch
>
>
> Zookeeper currently uses {{log4j 1.X}} as the default logging framework. 
> {{log4j 1.X}} is now deprecated http://logging.apache.org/log4j/1.2/
> This ticket is to track efforts to move zookeeper to {{log4j2}}



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

[jira] [Commented] (ZOOKEEPER-2659) Use log4j2 as a logging framework as log4j 1.X is now deprecated

[ASF GitHub Bot (JIRA)]

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

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

Github user praste closed the pull request at:

https://github.com/apache/zookeeper/pull/148


> Use log4j2 as a logging framework as log4j 1.X is now deprecated
> 
>
> Key: ZOOKEEPER-2659
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2659
> Project: ZooKeeper
>  Issue Type: Wish
>Reporter: Pushkar Raste
>Assignee: Pushkar Raste
>Priority: Minor
> Attachments: zk_log4j2_migration.patch
>
>
> Zookeeper currently uses {{log4j 1.X}} as the default logging framework. 
> {{log4j 1.X}} is now deprecated http://logging.apache.org/log4j/1.2/
> This ticket is to track efforts to move zookeeper to {{log4j2}}



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

[GitHub] zookeeper pull request #148: ZOOKEEPER-2659 Log4j 2 migration

[praste]

Github user praste closed the pull request at:

https://github.com/apache/zookeeper/pull/148


---
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.
---

[GitHub] zookeeper issue #148: ZOOKEEPER-2659 Log4j 2 migration

[praste]

Github user praste commented on the issue:

https://github.com/apache/zookeeper/pull/148
  
Looks like no one is really interested in this. 


---
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-2719) Port ZOOKEEPER-2169 to 3.5 branch

[ASF GitHub Bot (JIRA)]

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

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

Github user Randgalt closed the pull request at:

https://github.com/apache/zookeeper/pull/192


> Port ZOOKEEPER-2169 to 3.5 branch
> -
>
> Key: ZOOKEEPER-2719
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2719
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: java client, server
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Fix For: 3.5.3
>
>
> ZOOKEEPER-2169 is a useful feature that should be deployed sooner than later. 
> Take the work done in the master branch and port it to the 3.5 branch



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

[jira] [Commented] (ZOOKEEPER-2719) Port ZOOKEEPER-2169 to 3.5 branch

[ASF GitHub Bot (JIRA)]

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

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

Github user Randgalt commented on the issue:

https://github.com/apache/zookeeper/pull/192
  
merged into `branch-3.5`


> Port ZOOKEEPER-2169 to 3.5 branch
> -
>
> Key: ZOOKEEPER-2719
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2719
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: java client, server
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Fix For: 3.5.3
>
>
> ZOOKEEPER-2169 is a useful feature that should be deployed sooner than later. 
> Take the work done in the master branch and port it to the 3.5 branch



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

[GitHub] zookeeper pull request #192: ZOOKEEPER-2719: Pull changes for TTL Nodes into...

[Randgalt]

Github user Randgalt closed the pull request at:

https://github.com/apache/zookeeper/pull/192


---
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.
---

[GitHub] zookeeper issue #192: ZOOKEEPER-2719: Pull changes for TTL Nodes into 3.5 br...

[Randgalt]

Github user Randgalt commented on the issue:

https://github.com/apache/zookeeper/pull/192
  
merged into `branch-3.5`


---
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-2719) Port ZOOKEEPER-2169 to 3.5 branch

[ASF GitHub Bot (JIRA)]

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

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

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/192
  
Hi @Randgalt, congrats on getting this PR ported to 3.5! :smiley: Please, 
could you close this PR as it has been merged? Best regards!


> Port ZOOKEEPER-2169 to 3.5 branch
> -
>
> Key: ZOOKEEPER-2719
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2719
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: java client, server
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Fix For: 3.5.3
>
>
> ZOOKEEPER-2169 is a useful feature that should be deployed sooner than later. 
> Take the work done in the master branch and port it to the 3.5 branch



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

[GitHub] zookeeper issue #192: ZOOKEEPER-2719: Pull changes for TTL Nodes into 3.5 br...

[eribeiro]

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/192
  
Hi @Randgalt, congrats on getting this PR ported to 3.5! :smiley: Please, 
could you close this PR as it has been merged? Best regards!


---
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] [Updated] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[Rakesh R (JIRA)]

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

Rakesh R updated ZOOKEEPER-2712:

Priority: Critical  (was: Major)

> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.4.10
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



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

[jira] [Comment Edited] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[Rakesh R (JIRA)]

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

Rakesh R edited comment on ZOOKEEPER-2712 at 3/17/17 5:34 PM:
--

Thanks [~hanm] for the offline discussion about the static tool warnings.
{code}
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
{code}
Jira has broken links, am adding 
[patchJavadocWarnings.txt|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/patchprocess/patchJavadocWarnings.txt]
 link.

{code}
-1 findbugs. The patch appears to introduce 97 new Findbugs (version 3.0.1) 
warnings.
{code}
Jira has broken links, am adding 
[newPatchFindbugsWarnings.html|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/build/test/findbugs/newPatchFindbugsWarnings.html]
 link.

It looks like entire project items are showing and those are unrelated to the 
patch. The proposed fix is majorily touching test code apart from one source 
code QuorumPeer.java. So, anything required here?





was (Author: rakeshr):
Thanks [~hanm] for the offline discussion about the static tool warnings.
{code}
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
{code}
Jira has broken links, am adding 
[patchJavadocWarnings.txt|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/patchprocess/patchJavadocWarnings.txt]
 link.

{code}
-1 findbugs. The patch appears to introduce 97 new Findbugs (version 3.0.1) 
warnings.
{code}
Jira has broken links, am adding 
[newPatchFindbugsWarnings.html|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/build/test/findbugs/newPatchFindbugsWarnings.html]
 link.

It looks like entire project items are showing. The proposed fix is majorily 
touching test code apart from one source code QuorumPeer.java. So, anything 
required here?




> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



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

Failed: ZOOKEEPER- PreCommit Build #445

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/445/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.43 MB...]
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require 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 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/445//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/445//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/445//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] b8f81c4f00dc76d35e3fabac044b02924cf617d8 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: 13 minutes 50 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 578.70 KB of artifacts by 60.8% relative to #439
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[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



###
## FAILED TESTS (if any) 
##
1 tests failed.
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:1424)
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)

[jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2712:
-

Thanks [~hanm] for the offline discussion about the static tool warnings.
{code}
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
{code}
Jira has broken links, am adding 
[patchJavadocWarnings.txt|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/patchprocess/patchJavadocWarnings.txt]
 link.

{code}
-1 findbugs. The patch appears to introduce 97 new Findbugs (version 3.0.1) 
warnings.
{code}
Jira has broken links, am adding 
[newPatchFindbugsWarnings.html|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/build/test/findbugs/newPatchFindbugsWarnings.html]
 link.

It looks like entire project items are showing. The proposed fix is majorily 
touching test code apart from one source code QuorumPeer.java. So, anything 
required here?




> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



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

Contributing to Zookeeper

[Atri Sharma]

Hi All,

I am a distributed systems engineer with experience across different
spectrum of highly scalable systems and have worked with consistency
and quorum protocols.

I would be happy to help out on any ongoing/needed feature in
Zookeeper. Please let me know.


Regards,

Atri

ZooKeeper_branch35_openjdk7 - Build # 459 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/459/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.55 MB...]
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:22096
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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-03-17 16:13:49,962 [myid:] - INFO  [New I/O boss 
#2529:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-03-17 16:13:49,962 [myid:127.0.0.1:22096] - INFO  
[main-SendThread(127.0.0.1:22096):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x3004b2f2e0a0001 is lost, closing socket connection and attempting 
reconnect
[junit] 2017-03-17 16:13:50,074 [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-03-17 16:13:50,076 [myid:] - INFO  [New I/O boss 
#2772:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:22117
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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-03-17 16:13:50,076 [myid:] - WARN  [New I/O boss 
#2772:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x00c1144b] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:22117
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:22117
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[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-03-17 16:13:50,076 

[jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[Rakesh R (JIRA)]

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

Rakesh R commented on ZOOKEEPER-2712:
-

[~hanm], Yes the test cases are happily running in my Windows env. Later, I 
have tried running in Linux and it is failing. After putting the delay between 
the server startup, I could see it is passing consistently.

[~hanm], [~phunt], It would be really helpful if you could post your feedback 
on the proposed fix. Thanks!


> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



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

[jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2712:
--

-1 overall.  GitHub Pull Request  Build
  

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

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

-1 javadoc.  The javadoc tool appears to have generated 1 warning messages.

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

-1 findbugs.  The patch appears to introduce 97 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/444//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444//console

This message is automatically generated.

> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



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

Failed: ZOOKEEPER- PreCommit Build #444

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34.86 MB...]
 [exec] +1 tests included.  The patch appears to include 18 new or 
modified tests.
 [exec] 
 [exec] -1 javadoc.  The javadoc tool appears to have generated 1 
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 97 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/444//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444//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] 813ec7fc9ccf7ac4a1b8d9ceafdd8d53dd07aba9 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:1714:
 exec returned: 2

Total time: 35 minutes 20 seconds
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
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2712
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) 
##
All tests passed

ZooKeeper_branch35_jdk7 - Build # 892 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/892/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 62.78 MB...]
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-17 15:49:06,889 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=Connections,name2=127.0.0.1,name3=0x1030827c79c]
[junit] 2017-03-17 15:49:06,990 [myid:] - INFO  [main:ZooKeeper@1326] - 
Session: 0x1030827c79c closed
[junit] 2017-03-17 15:49:06,990 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 240319
[junit] 2017-03-17 15:49:06,990 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1030827c79c
[junit] 2017-03-17 15:49:06,990 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2428
[junit] 2017-03-17 15:49:06,991 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-17 15:49:06,991 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2017-03-17 15:49:06,991 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2017-03-17 15:49:06,991 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14161
[junit] 2017-03-17 15:49:06,999 [myid:] - INFO  [main:ZooKeeperServer@541] 
- shutting down
[junit] 2017-03-17 15:49:06,999 [myid:] - ERROR [main:ZooKeeperServer@505] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 15:49:06,999 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-17 15:49:07,000 [myid:] - INFO  
[main:PrepRequestProcessor@1004] - Shutting down
[junit] 2017-03-17 15:49:07,000 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-17 15:49:07,000 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop!
[junit] 2017-03-17 15:49:07,000 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-17 15:49:07,001 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-17 15:49:07,001 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=InMemoryDataTree]
[junit] 2017-03-17 15:49:07,001 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14161]
[junit] 2017-03-17 15:49:07,002 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 14161
[junit] 2017-03-17 15:49:07,002 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-03-17 15:49:07,014 [myid:] - INFO  [main:ClientBase@568] - 
fdcount after test is: 7135 at start it was 7135
[junit] 2017-03-17 15:49:07,014 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-03-17 15:49:07,014 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] 2017-03-17 15:49:07,042 [myid:127.0.0.1:14044] - INFO  
[main-SendThread(127.0.0.1:14044):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14044. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-17 15:49:07,043 [myid:127.0.0.1:14044] - WARN  
[main-SendThread(127.0.0.1:14044):ClientCnxn$SendThread@1235] - Session 
0x30308248cc9 for server 127.0.0.1/127.0.0.1:14044, 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:744)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
466.58 sec, Thread: 2, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-03-17 15:49:07,371 [myid:127.0.0.1:14041] - INFO  
[main-SendThread(127.0.0.1:14041):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14041. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-17 15:49:07,372 [myid:127.0.0.1:14041] - WARN  
[main-SendThread(127.0.0.1:14041):ClientCnxn$SendThread@1235] - Session 
0x20308248cc6 for server 127.0.0.1/127.0.0.1:14041, unexpected 

[jira] [Created] (ZOOKEEPER-2727) WARN and stacktrace for normally closed socket

[Andrey (JIRA)]

Andrey created ZOOKEEPER-2727:
-

 Summary: WARN and stacktrace for normally closed socket
 Key: ZOOKEEPER-2727
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2727
 Project: ZooKeeper
  Issue Type: Bug
Affects Versions: 3.4.9
Reporter: Andrey


Steps to reproduce:
* setup zookeeper
* setup TCP load balancer. This balancer should check zookeeper clientPort 
liveness(healthcheck) by opening and closing TCP connection to clientPort. See 
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/
 or 
https://www.digitalocean.com/community/tutorials/how-to-create-your-first-digitalocean-load-balancer#step-2-—-creating-the-load-balancer
 for details. 
* in logs:
{code}
2017-03-17 15:41:19,843 [myid:1] - WARN  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of 
stream exception
EndOfStreamException: Unable to read additional data from client sessionid 0x0, 
likely client has closed socket
at 
org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
at 
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
at java.lang.Thread.run(Thread.java:745)
{code}

Issue is here:
https://github.com/apache/zookeeper/blob/5fe68506f217246c7ebd96803f9c78e13ec2f11a/src/java/main/org/apache/zookeeper/server/NIOServerCnxn.java#L322

-1 is a normal socket termination. 

Expected:
* reduce log level to INFO
* do not log stacktrace.



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

3.5.3: alpha or beta?

[Liang Han]

Hi all,

I noticed that in JIRA the 3.5.3 is still tagged as Alpha [1]. Also this is
mentioned in last board meeting [2] that 3.5.3 will be last Alpha release,
as opposed to a new beta release.

I thought sometime back we agreed that 3.5.3 would be a beta release,
because we intended to lock the APIs for this release? 3.5.3-beta was
originally mentioned a couple years ago when 3.5 series releases was
planned [3] where the semantic of alpha and beta was also clarified, but I
can't find any traces on why 3.5.3 was named Alpha on JIRA.

Should we make 3.5.3 another alpha release, or a beta release?

[1]
https://issues.apache.org/jira/browse/ZOOKEEPER/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
[2] https://whimsy.apache.org/board/minutes/ZooKeeper.html
[3]
http://markmail.org/message/vnb5pvszgm4cty67#query:+page:1+mid:ymxliy2rrwjc2pmo+state:results

-- 
Cheers
Michael.

[jira] [Updated] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[Rakesh R (JIRA)]

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

Rakesh R updated ZOOKEEPER-2712:

Fix Version/s: (was: 3.4.11)
   3.4.10

> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



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

[jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[ASF GitHub Bot (JIRA)]

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

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

GitHub user rakeshadr opened a pull request:

https://github.com/apache/zookeeper/pull/200

ZOOKEEPER-2712: MiniKdc test case intermittently failing due to princ…

After long long analysis, I have observed concurrency issues at `ApacheDs 
`(used for unit test) causing the trouble and failing minikdc test cases. 
Introduced delay between the ZK server's startup to avoid simultaneous login 
context init across servers. Also, modified few test code for better debugging.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rakeshadr/zookeeper-1 ZK-2712

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/200.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #200


commit 3d1db97770a23ab8a9d9dd5700544518f865647a
Author: Rakesh Radhakrishnan 
Date:   2017-03-17T15:25:56Z

ZOOKEEPER-2712: MiniKdc test case intermittently failing due to principal 
not found in Kerberos database




> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



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

[GitHub] zookeeper pull request #200: ZOOKEEPER-2712: MiniKdc test case intermittentl...

[rakeshadr]

GitHub user rakeshadr opened a pull request:

https://github.com/apache/zookeeper/pull/200

ZOOKEEPER-2712: MiniKdc test case intermittently failing due to princ…

After long long analysis, I have observed concurrency issues at `ApacheDs 
`(used for unit test) causing the trouble and failing minikdc test cases. 
Introduced delay between the ZK server's startup to avoid simultaneous login 
context init across servers. Also, modified few test code for better debugging.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rakeshadr/zookeeper-1 ZK-2712

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/200.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #200


commit 3d1db97770a23ab8a9d9dd5700544518f865647a
Author: Rakesh Radhakrishnan 
Date:   2017-03-17T15:25:56Z

ZOOKEEPER-2712: MiniKdc test case intermittently failing due to principal 
not found in Kerberos database




---
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.
---

ZooKeeper_branch34_openjdk7 - Build # 1432 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1432/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 30.24 MB...]
[junit] 2017-03-17 15:21:14,594 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-17 15:21:14,594 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-17 15:21:14,594 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-17 15:21:14,595 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-17 15:21:14,595 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-17 15:21:14,595 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-17 15:21:14,595 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-17 15:21:14,596 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-17 15:21:14,597 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-17 15:21:14,597 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-17 15:21:14,597 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-17 15:21:14,598 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-17 15:21:14,598 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/build/test/tmp/test1983158256101735144.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/build/test/tmp/test1983158256101735144.junit.dir/version-2
[junit] 2017-03-17 15:21:14,601 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 15:21:14,601 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-17 15:21:14,602 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:52747
[junit] 2017-03-17 15:21:14,602 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:52747
[junit] 2017-03-17 15:21:14,603 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-17 15:21:14,603 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:52747 (no session established for client)
[junit] 2017-03-17 15:21:14,603 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-17 15:21:14,605 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-17 15:21:14,605 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-17 15:21:14,605 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-17 15:21:14,605 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-17 15:21:14,605 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35724
[junit] 2017-03-17 15:21:14,606 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-17 15:21:14,606 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-17 15:21:14,606 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-17 15:21:14,680 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15adcdbc372 closed
[junit] 2017-03-17 15:21:14,680 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-17 15:21:14,681 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15adcdbc372
[junit] 2017-03-17 15:21:14,681 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-17 15:21:14,681 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-17 15:21:14,681 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 

[jira] [Resolved] (ZOOKEEPER-2719) Port ZOOKEEPER-2169 to 3.5 branch

[Camille Fournier (JIRA)]

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

Camille Fournier resolved ZOOKEEPER-2719.
-
Resolution: Fixed

Issue resolved by pull request 192
[https://github.com/apache/zookeeper/pull/192]

> Port ZOOKEEPER-2169 to 3.5 branch
> -
>
> Key: ZOOKEEPER-2719
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2719
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: java client, server
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Fix For: 3.5.3
>
>
> ZOOKEEPER-2169 is a useful feature that should be deployed sooner than later. 
> Take the work done in the master branch and port it to the 3.5 branch



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

Failed: ZOOKEEPER- PreCommit Build #443

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/443/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2.04 KB...]
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H7(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
at com.sun.proxy.$Proxy80.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:324)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:995)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1102)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 
origin/trunk" returned status code 1:
stdout: 
stderr: error: pathspec 'origin/trunk' did not match any file(s) known to git.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:64)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2060)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:81)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:894)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

[jira] [Commented] (ZOOKEEPER-2724) Skip cert files for releaseaudit target.

[ASF GitHub Bot (JIRA)]

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

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

Github user hanm closed the pull request at:

https://github.com/apache/zookeeper/pull/194


> Skip cert files for releaseaudit target.
> 
>
> Key: ZOOKEEPER-2724
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2724
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Blocker
>  Labels: build
> Fix For: 3.5.3
>
>
> In branch-3.5 release auditing generating warnings against cert files as 
> these files don't contain Apache License (AL) header. I don't think these 
> files should be checked because they are not source files, and we skip them 
> in master branch. We should do the same for branch-3.5 by skipping these cert 
> files as well. This should be fixed before 3.5.3 release.
> Attach the snippet of warning for reference:
> {noformat}
> [rat:report]  !? 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build/zookeeper-3.5.3-alpha-SNAPSHOT/contrib/rest/conf/keys/rest.cer
> [rat:report]  !? 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build/zookeeper-3.5.3-alpha-SNAPSHOT/src/contrib/rest/conf/keys/rest.cer
> {noformat}



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

[GitHub] zookeeper pull request #194: ZOOKEEPER-2724: Skip cert files for releaseaudi...

[hanm]

Github user hanm closed the pull request at:

https://github.com/apache/zookeeper/pull/194


---
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.
---

Failed: ZOOKEEPER- PreCommit Build #442

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/442/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2.04 KB...]
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H7(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
at com.sun.proxy.$Proxy80.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:324)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:995)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1102)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 
origin/trunk" returned status code 1:
stdout: 
stderr: error: pathspec 'origin/trunk' did not match any file(s) known to git.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:64)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2060)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:81)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:894)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

[jira] [Resolved] (ZOOKEEPER-2724) Skip cert files for releaseaudit target.

[Camille Fournier (JIRA)]

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

Camille Fournier resolved ZOOKEEPER-2724.
-
Resolution: Fixed

> Skip cert files for releaseaudit target.
> 
>
> Key: ZOOKEEPER-2724
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2724
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Blocker
>  Labels: build
> Fix For: 3.5.3
>
>
> In branch-3.5 release auditing generating warnings against cert files as 
> these files don't contain Apache License (AL) header. I don't think these 
> files should be checked because they are not source files, and we skip them 
> in master branch. We should do the same for branch-3.5 by skipping these cert 
> files as well. This should be fixed before 3.5.3 release.
> Attach the snippet of warning for reference:
> {noformat}
> [rat:report]  !? 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build/zookeeper-3.5.3-alpha-SNAPSHOT/contrib/rest/conf/keys/rest.cer
> [rat:report]  !? 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build/zookeeper-3.5.3-alpha-SNAPSHOT/src/contrib/rest/conf/keys/rest.cer
> {noformat}



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

ZooKeeper_branch35_jdk8 - Build # 459 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/459/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 62.37 MB...]
[junit] 2017-03-17 12:12:48,784 [myid:127.0.0.1:14161] - INFO  
[main-SendThread(127.0.0.1:14161):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14161. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-17 12:12:48,784 [myid:127.0.0.1:14161] - INFO  
[main-SendThread(127.0.0.1:14161):ClientCnxn$SendThread@948] - Socket 
connection established, initiating session, client: /127.0.0.1:47250, server: 
127.0.0.1/127.0.0.1:14161
[junit] 2017-03-17 12:12:48,785 [myid:] - INFO  [New I/O worker 
#1829:ZooKeeperServer@1018] - Client attempting to renew session 
0x10421fe5be8 at /127.0.0.1:47250
[junit] 2017-03-17 12:12:48,786 [myid:] - INFO  [New I/O worker 
#1829:ZooKeeperServer@727] - Established session 0x10421fe5be8 with 
negotiated timeout 6000 for client /127.0.0.1:47250
[junit] 2017-03-17 12:12:48,786 [myid:127.0.0.1:14161] - INFO  
[main-SendThread(127.0.0.1:14161):ClientCnxn$SendThread@1381] - Session 
establishment complete on server 127.0.0.1/127.0.0.1:14161, sessionid = 
0x10421fe5be8, negotiated timeout = 6000
[junit] 2017-03-17 12:12:48,788 [myid:] - INFO  
[SyncThread:0:FileTxnLog@204] - Creating new log file: log.7
[junit] 2017-03-17 12:12:49,245 [myid:127.0.0.1:13915] - INFO  
[main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:13915. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-17 12:12:49,245 [myid:127.0.0.1:13915] - WARN  
[main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1235] - Session 
0x10421f7d373 for server 127.0.0.1/127.0.0.1:13915, 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-03-17 12:12:49,805 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@655] - Processed session termination for 
sessionid: 0x10421fe5be8
[junit] 2017-03-17 12:12:49,807 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=Connections,name2=127.0.0.1,name3=0x10421fe5be8]
[junit] 2017-03-17 12:12:49,807 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10421fe5be8
[junit] 2017-03-17 12:12:49,808 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x10421fe5be8 closed
[junit] 2017-03-17 12:12:49,808 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 111247
[junit] 2017-03-17 12:12:49,808 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 467
[junit] 2017-03-17 12:12:49,808 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-17 12:12:49,808 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2017-03-17 12:12:49,808 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2017-03-17 12:12:49,808 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14161
[junit] 2017-03-17 12:12:49,809 [myid:] - INFO  [main:ZooKeeperServer@541] 
- shutting down
[junit] 2017-03-17 12:12:49,809 [myid:] - ERROR [main:ZooKeeperServer@505] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 12:12:49,809 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-17 12:12:49,809 [myid:] - INFO  
[main:PrepRequestProcessor@973] - Shutting down
[junit] 2017-03-17 12:12:49,809 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-17 12:12:49,809 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop!
[junit] 2017-03-17 12:12:49,810 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-17 12:12:49,810 [myid:] - INFO  
[main:FinalRequestProcessor@479] - shutdown of request processor complete
[junit] 2017-03-17 12:12:49,810 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 

[jira] [Updated] (ZOOKEEPER-2717) org.apache.zookeeper.server.quorum.RaceConditionTest fails intermittently

[Sneha Kanekar (JIRA)]

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

Sneha Kanekar updated ZOOKEEPER-2717:
-
Environment: Ubuntu:14.04  (was: Linux 6945c232192e 3.16.0-30-generic 
#40~14.04.1-Ubuntu SMP Thu Jan 15 17:42:36 UTC 2015 ppc64le ppc64le ppc64le 
GNU/Linux)
 Labels: ppc64le x86  (was: ppc64le)
Description: 
The test-suite org.apache.zookeeper.server.quorum.RaceConditionTest fails 
intermittently on ppc64le and x86 architechture with following error message:
{code:borderStyle=solid}
org.apache.zookeeper.server.quorum.RaceConditionTest.testRaceConditionBetweenLeaderAndAckRequestProcessor

Stacktrace:

Leader failed to transition to new state. Current state is leading
junit.framework.AssertionFailedError: Leader failed to transition to new state. 
Current state is leading
at 
org.apache.zookeeper.server.quorum.RaceConditionTest.testRaceConditionBetweenLeaderAndAckRequestProcessor(RaceConditionTest.java:82)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:745)

{code}

Also I have attached the standard output log file.

  was:
The test-suite org.apache.zookeeper.server.quorum.RaceConditionTest fails 
intermittently on ppc64le with following error message:
{code:borderStyle=solid}
org.apache.zookeeper.server.quorum.RaceConditionTest.testRaceConditionBetweenLeaderAndAckRequestProcessor

Stacktrace:

Leader failed to transition to new state. Current state is leading
junit.framework.AssertionFailedError: Leader failed to transition to new state. 
Current state is leading
at 
org.apache.zookeeper.server.quorum.RaceConditionTest.testRaceConditionBetweenLeaderAndAckRequestProcessor(RaceConditionTest.java:82)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:745)

{code}

Also I have attached the standard output log file.


> org.apache.zookeeper.server.quorum.RaceConditionTest fails intermittently
> -
>
> Key: ZOOKEEPER-2717
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2717
> Project: ZooKeeper
>  Issue Type: Test
>  Components: quorum, server, tests
>Affects Versions: 3.6.0
> Environment: Ubuntu:14.04
>Reporter: Sneha Kanekar
>  Labels: ppc64le, x86
> Attachments: RaceConditionTestErrorLog.txt
>
>
> The test-suite org.apache.zookeeper.server.quorum.RaceConditionTest fails 
> intermittently on ppc64le and x86 architechture with following error message:
> {code:borderStyle=solid}
> org.apache.zookeeper.server.quorum.RaceConditionTest.testRaceConditionBetweenLeaderAndAckRequestProcessor
> Stacktrace:
> Leader failed to transition to new state. Current state is leading
> junit.framework.AssertionFailedError: Leader failed to transition to new 
> state. Current state is leading
> at 
> org.apache.zookeeper.server.quorum.RaceConditionTest.testRaceConditionBetweenLeaderAndAckRequestProcessor(RaceConditionTest.java:82)
> at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Also I have attached the standard output log file.



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

ZooKeeper_branch35_openjdk7 - Build # 458 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/458/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 14.25 MB...]
[junit] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[junit] at java.lang.reflect.Method.invoke(Method.java:606)
[junit] at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
[junit] at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
[junit] at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
[junit] at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
[junit] at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
[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 
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-03-17 09:59:34,228 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 27431
[junit] 2017-03-17 09:59:34,230 [myid:1] - INFO  
[NIOServerCxnFactory.AcceptThread:/0.0.0.0:27431:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:59784
[junit] 2017-03-17 09:59:34,253 [myid:1] - INFO  
[NIOWorkerThread-7:NIOServerCnxn@518] - Processing stat command from 
/127.0.0.1:59784
[junit] 2017-03-17 09:59:34,253 [myid:1] - INFO  
[NIOWorkerThread-7:StatCommand@49] - Stat command output
[junit] 2017-03-17 09:59:34,253 [myid:1] - INFO  
[NIOWorkerThread-7:NIOServerCnxn@627] - Closed socket connection for client 
/127.0.0.1:59784 (no session established for client)
[junit] 2017-03-17 09:59:34,254 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 27432
[junit] 2017-03-17 09:59:34,255 [myid:2] - INFO  
[NIOServerCxnFactory.AcceptThread:/0.0.0.0:27432:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:51116
[junit] 2017-03-17 09:59:34,256 [myid:2] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@518] - Processing stat command from 
/127.0.0.1:51116
[junit] 2017-03-17 09:59:34,256 [myid:2] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2017-03-17 09:59:34,256 [myid:2] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@627] - Closed socket connection for client 
/127.0.0.1:51116 (no session established for client)
[junit] 2017-03-17 09:59:34,257 [myid:1] - INFO  
[/127.0.0.1:27433:QuorumCnxManager$Listener@642] - Received connection request 
/127.0.0.1:43863
[junit] 2017-03-17 09:59:34,257 [myid:1] - WARN  
[/127.0.0.1:27433:QuorumCnxManager@346] - Exception reading or writing 
challenge: java.io.EOFException
[junit] 2017-03-17 09:59:34,258 [myid:] - INFO  [main:ZooKeeper@863] - 
Initiating client connection, connectString=127.0.0.1:27431 
sessionTimeout=3 
watcher=org.apache.zookeeper.server.quorum.QuorumPeerMainTest@4d7467e5
[junit] 2017-03-17 09:59:34,260 [myid:] - INFO  [main:ClientCnxnSocket@236] 
- jute.maxbuffer value is 4194304 Bytes
[junit] 2017-03-17 09:59:34,262 [myid:2] - INFO  
[/127.0.0.1:27434:QuorumCnxManager$Listener@642] - Received connection request 
/127.0.0.1:42286
[junit] 2017-03-17 09:59:34,262 [myid:2] - WARN  
[/127.0.0.1:27434:QuorumCnxManager@346] - Exception reading or writing 
challenge: java.io.EOFException
[junit] 2017-03-17 09:59:34,266 [myid:127.0.0.1:27431] - INFO  
[main-SendThread(127.0.0.1:27431):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27431. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-17 

[jira] [Commented] (ZOOKEEPER-2184) Zookeeper Client should re-resolve hosts when connection attempts fail

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2184:
--

-1 overall.  GitHub Pull Request  Build
  

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

+1 tests included.  The patch appears to include 75 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/441//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/441//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/441//console

This message is automatically generated.

> Zookeeper Client should re-resolve hosts when connection attempts fail
> --
>
> Key: ZOOKEEPER-2184
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.6, 3.5.0
> Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & 
> Kafka
>Reporter: Robert P. Thille
>Assignee: Flavio Junqueira
>  Labels: easyfix, patch
> Fix For: 3.5.4, 3.6.0, 3.4.11
>
> Attachments: ZOOKEEPER-2184.patch
>
>
> Testing in a Docker environment with a single Kafka instance using a single 
> Zookeeper instance. Restarting the Zookeeper container will cause it to 
> receive a new IP address. Kafka will never be able to reconnect to Zookeeper 
> and will hang indefinitely. Updating DNS or /etc/hosts with the new IP 
> address will not help the client to reconnect as the 
> zookeeper/client/StaticHostProvider resolves the connection string hosts at 
> creation time and never re-resolves.
> A solution would be for the client to notice that connection attempts fail 
> and attempt to re-resolve the hostnames in the connectString.



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

Failed: ZOOKEEPER- PreCommit Build #441

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/441/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.76 MB...]
 [exec] +1 tests included.  The patch appears to include 75 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 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/441//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/441//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/441//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] d74eece36828b6f0ca1f1f7a90b808731c6066f4 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:1641:
 exec returned: 1

Total time: 18 minutes 38 seconds
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
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2184
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) 
##
All tests passed

Failed: ZOOKEEPER- PreCommit Build #440

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/440/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.90 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 generated 2 release audit 
warnings (more than the trunk's current 0 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/440//testReport/
 [exec] Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/440//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/440//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/440//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] 0dde362e10524350da28dbcfaa8f05ee96125644 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:1641:
 exec returned: 2

Total time: 13 minutes 32 seconds
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
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2184
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.test.CnxManagerTest.testCnxManagerTimeout

Error Message:
Waited more than necessary

Stack Trace:
junit.framework.AssertionFailedError: Waited more than necessary
at 
org.apache.zookeeper.test.CnxManagerTest.testCnxManagerTimeout(CnxManagerTest.java:216)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Commented] (ZOOKEEPER-2184) Zookeeper Client should re-resolve hosts when connection attempts fail

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-2184:
--

-1 overall.  GitHub Pull Request  Build
  

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

+1 tests included.  The patch appears to include 75 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 generated 2 release audit warnings 
(more than the trunk's current 0 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/440//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/440//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/440//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/440//console

This message is automatically generated.

> Zookeeper Client should re-resolve hosts when connection attempts fail
> --
>
> Key: ZOOKEEPER-2184
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2184
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.6, 3.5.0
> Environment: Ubuntu 14.04 host, Docker containers for Zookeeper & 
> Kafka
>Reporter: Robert P. Thille
>Assignee: Flavio Junqueira
>  Labels: easyfix, patch
> Fix For: 3.5.4, 3.6.0, 3.4.11
>
> Attachments: ZOOKEEPER-2184.patch
>
>
> Testing in a Docker environment with a single Kafka instance using a single 
> Zookeeper instance. Restarting the Zookeeper container will cause it to 
> receive a new IP address. Kafka will never be able to reconnect to Zookeeper 
> and will hang indefinitely. Updating DNS or /etc/hosts with the new IP 
> address will not help the client to reconnect as the 
> zookeeper/client/StaticHostProvider resolves the connection string hosts at 
> creation time and never re-resolves.
> A solution would be for the client to notice that connection attempts fail 
> and attempt to re-resolve the hostnames in the connectString.



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