[jira] [Commented] (ZOOKEEPER-2857) Server deal command has problem

[maoling (JIRA)]

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

maoling commented on ZOOKEEPER-2857:


Initialized may be a flag that distinguishes a real client connection from a 
cmd fourletter .the main logic is in NIOServerCnxn#doIO and I debug it using 
org.apache.zookeeper.server.quorum.WatchLeakTest#testWatchesLeak.can you give 
more your description?

> Server deal command has problem
> ---
>
> Key: ZOOKEEPER-2857
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2857
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.3.0
>Reporter: Bo Hu
>
> NIOServerCnxn.java
> private boolean readLength(SelectionKey k) throws IOException 
> if (!initialized && checkFourLetterWord(sk, len)) {
> return false;
> }
> I think this is a problem. when initialized is true, it also need execute 
> checkFourLetterWord, but it don't execute.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Success: ZOOKEEPER- PreCommit Build #910

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34.53 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [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 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/910//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/910//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/910//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] 39f7a7cf421e83960703291cac517a2220e8e6cc 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: 35 minutes 8 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-1669
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



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

[jira] [Commented] (ZOOKEEPER-1669) Operations to server will be timed-out while thousands of sessions expired same time

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-1669:
--

+1 overall.  GitHub Pull Request  Build
  

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

+0 tests included.  The patch appears to be a documentation patch that 
doesn't require 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/910//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/910//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/910//console

This message is automatically generated.

> Operations to server will be timed-out while thousands of sessions expired 
> same time
> 
>
> Key: ZOOKEEPER-1669
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1669
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.5
>Reporter: tokoot
>Assignee: Cheney Sun
>  Labels: performance
>
> If there are thousands of clients, and most of them disconnect with server 
> same time(client restarted or servers partitioned with clients), the server 
> will busy to close those "connections" and become unavailable. The problem is 
> in following:
>   private void closeSessionWithoutWakeup(long sessionId) {
>   HashSet cnxns;
>   synchronized (this.cnxns) {
>   cnxns = (HashSet)this.cnxns.clone();  // other 
> thread will block because of here
>   }
>   ...
>   }
> A real world example that demonstrated this problem (Kudos to [~sun.cheney]):
> {noformat}
> The issue is raised while tens thousands of clients try to reconnect 
> ZooKeeper service. 
> Actually, we came across the issue during maintaining our HBase cluster, 
> which used a 5-server ZooKeeper cluster. 
> The HBase cluster was composed of many many regionservers (in thousand order 
> of magnitude), 
> and connected by tens thousands of clients to do massive reads/writes. 
> Because the r/w throughput is very high, ZooKeeper zxid increased quickly as 
> well. 
> Basically, each two or three weeks, Zookeeper would make leader relection 
> triggered by the zxid roll over. 
> The leader relection will cause the clients(HBase regionservers and HBase 
> clients) disconnected 
> and reconnected with Zookeeper servers in the mean time, and try to renew the 
> sessions.
> In current implementation of session renew, NIOServerCnxnFactory will clone 
> all the connections at first 
> in order to avoid race condition in multi-threads and go iterate the cloned 
> connection set one by one to 
> find the related session to renew. It's very time consuming. In our case 
> (described above), 
> it caused many region servers can't successfully renew session before session 
> timeout, 
> and eventually the HBase cluster lose these region servers and affect the 
> HBase stability.
> The change is to make refactoring to the close session logic and introduce a 
> ConcurrentHashMap 
> to store session id and connection map relation, which is a thread-safe data 
> structure 
> and eliminate the necessary to clone the connection set at first.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-1669) Operations to server will be timed-out while thousands of sessions expired same time

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/zookeeper/pull/312#discussion_r130259699
  
--- Diff: src/java/main/org/apache/zookeeper/server/ServerCnxn.java ---
@@ -101,6 +102,13 @@ public boolean removeAuthInfo(Id id) {
 
 abstract void setSessionTimeout(int sessionTimeout);
 
+/**
+ * Wrapper method to return the socket address
+ */
+public InetAddress getSocketAddress() {
--- End diff --

fixed. Thanks @eribeiro .


> Operations to server will be timed-out while thousands of sessions expired 
> same time
> 
>
> Key: ZOOKEEPER-1669
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1669
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.5
>Reporter: tokoot
>Assignee: Cheney Sun
>  Labels: performance
>
> If there are thousands of clients, and most of them disconnect with server 
> same time(client restarted or servers partitioned with clients), the server 
> will busy to close those "connections" and become unavailable. The problem is 
> in following:
>   private void closeSessionWithoutWakeup(long sessionId) {
>   HashSet cnxns;
>   synchronized (this.cnxns) {
>   cnxns = (HashSet)this.cnxns.clone();  // other 
> thread will block because of here
>   }
>   ...
>   }
> A real world example that demonstrated this problem (Kudos to [~sun.cheney]):
> {noformat}
> The issue is raised while tens thousands of clients try to reconnect 
> ZooKeeper service. 
> Actually, we came across the issue during maintaining our HBase cluster, 
> which used a 5-server ZooKeeper cluster. 
> The HBase cluster was composed of many many regionservers (in thousand order 
> of magnitude), 
> and connected by tens thousands of clients to do massive reads/writes. 
> Because the r/w throughput is very high, ZooKeeper zxid increased quickly as 
> well. 
> Basically, each two or three weeks, Zookeeper would make leader relection 
> triggered by the zxid roll over. 
> The leader relection will cause the clients(HBase regionservers and HBase 
> clients) disconnected 
> and reconnected with Zookeeper servers in the mean time, and try to renew the 
> sessions.
> In current implementation of session renew, NIOServerCnxnFactory will clone 
> all the connections at first 
> in order to avoid race condition in multi-threads and go iterate the cloned 
> connection set one by one to 
> find the related session to renew. It's very time consuming. In our case 
> (described above), 
> it caused many region servers can't successfully renew session before session 
> timeout, 
> and eventually the HBase cluster lose these region servers and affect the 
> HBase stability.
> The change is to make refactoring to the close session logic and introduce a 
> ConcurrentHashMap 
> to store session id and connection map relation, which is a thread-safe data 
> structure 
> and eliminate the necessary to clone the connection set at first.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #312: ZOOKEEPER-1669: Operations to server will be ti...

[CheneySun]

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

https://github.com/apache/zookeeper/pull/312#discussion_r130259699
  
--- Diff: src/java/main/org/apache/zookeeper/server/ServerCnxn.java ---
@@ -101,6 +102,13 @@ public boolean removeAuthInfo(Id id) {
 
 abstract void setSessionTimeout(int sessionTimeout);
 
+/**
+ * Wrapper method to return the socket address
+ */
+public InetAddress getSocketAddress() {
--- End diff --

fixed. Thanks @eribeiro .


---
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-trunk - Build # 3484 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 66.35 MB...]
[junit] 2017-07-30 23:26:26,526 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-07-30 23:26:26,526 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-07-30 23:26:26,526 [myid:] - INFO  [ProcessThread(sid:0 
cport:30319)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop!
[junit] 2017-07-30 23:26:26,526 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-07-30 23:26:26,527 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-07-30 23:26:26,527 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port30319,name1=InMemoryDataTree]
[junit] 2017-07-30 23:26:26,527 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port30319]
[junit] 2017-07-30 23:26:26,527 [myid:] - INFO  
[main:FourLetterWordMain@87] - connecting to 127.0.0.1 30319
[junit] 2017-07-30 23:26:26,528 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-07-30 23:26:26,534 [myid:127.0.0.1:30199] - INFO  
[main-SendThread(127.0.0.1:30199):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30199. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-07-30 23:26:26,535 [myid:127.0.0.1:30199] - WARN  
[main-SendThread(127.0.0.1:30199):ClientCnxn$SendThread@1235] - Session 
0x205bf7f8d26 for server 127.0.0.1/127.0.0.1:30199, 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] 2017-07-30 23:26:26,539 [myid:] - INFO  [main:ClientBase@626] - 
fdcount after test is: 7147 at start it was 7147
[junit] 2017-07-30 23:26:26,539 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-07-30 23:26:26,539 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
404.919 sec, Thread: 8, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-07-30 23:26:26,568 [myid:127.0.0.1:30196] - INFO  
[main-SendThread(127.0.0.1:30196):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30196. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-07-30 23:26:26,607 [myid:127.0.0.1:30196] - WARN  
[main-SendThread(127.0.0.1:30196):ClientCnxn$SendThread@1235] - Session 
0x105bf7f8943 for server 127.0.0.1/127.0.0.1:30196, 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] 2017-07-30 23:26:26,753 [myid:127.0.0.1:30202] - INFO  
[main-SendThread(127.0.0.1:30202):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30202. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-07-30 23:26:26,753 [myid:127.0.0.1:30202] - WARN  
[main-SendThread(127.0.0.1:30202):ClientCnxn$SendThread@1235] - Session 
0x305bf7f8948 for server 127.0.0.1/127.0.0.1:30202, 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)

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1339: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1220: The 
following erro

ZooKeeper_branch34_jdk8 - Build # 1079 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 30.11 MB...]
[junit] 2017-07-30 23:12:43,622 [myid:] - INFO  
[main:PrepRequestProcessor@769] - Shutting down
[junit] 2017-07-30 23:12:43,622 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-07-30 23:12:43,622 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@144] - PrepRequestProcessor exited loop!
[junit] 2017-07-30 23:12:43,623 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-07-30 23:12:43,623 [myid:] - INFO  
[main:FinalRequestProcessor@403] - shutdown of request processor complete
[junit] 2017-07-30 23:12:43,623 [myid:] - INFO  
[main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221
[junit] 2017-07-30 23:12:43,624 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-07-30 23:12:43,625 [myid:] - INFO  [main:ClientBase@489] - 
STARTING server
[junit] 2017-07-30 23:12:43,625 [myid:] - INFO  [main:ClientBase@410] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-07-30 23:12:43,625 [myid:] - INFO  
[main:ServerCnxnFactory@111] - Using 
org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory
[junit] 2017-07-30 23:12:43,626 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-07-30 23:12:43,626 [myid:] - INFO  [main:ClientBase@385] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-07-30 23:12:43,626 [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/test7979865770648767053.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test7979865770648767053.junit.dir/version-2
[junit] 2017-07-30 23:12:43,629 [myid:] - ERROR [main:ZooKeeperServer@468] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-07-30 23:12:43,630 [myid:] - INFO  
[main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221
[junit] 2017-07-30 23:12:43,635 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:38544
[junit] 2017-07-30 23:12:43,635 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:38544
[junit] 2017-07-30 23:12:43,635 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-07-30 23:12:43,636 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:38544 (no session established for client)
[junit] 2017-07-30 23:12:43,636 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-07-30 23:12:43,638 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-07-30 23:12:43,638 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-07-30 23:12:43,638 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-07-30 23:12:43,638 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-07-30 23:12:43,639 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35542
[junit] 2017-07-30 23:12:43,639 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-07-30 23:12:43,639 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-07-30 23:12:43,639 [myid:] - INFO  [main:ClientBase@566] - 
tearDown starting
[junit] 2017-07-30 23:12:43,710 [myid:] - INFO  [main:ZooKeeper@687] - 
Session: 0x105c093962b closed
[junit] 2017-07-30 23:12:43,710 [myid:] - INFO  [main:ClientBase@536] - 
STOPPING server
[junit] 2017-07-30 23:12:43,710 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@520] - EventThread shut down for 
session: 0x105c093962b
[junit] 2017-07-30 23:12:43,711 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-07-30 23:12:43,711 [myid:] - INFO  [main:ZooKeeperServer@501] 
- shutting down
[junit] 2017-07-30 23:12:43,711 [myid:] - ERROR [main:ZooKeeperServer@468] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or

Success: ZOOKEEPER- PreCommit Build #909

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34.18 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 3 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 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/909//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/909//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/909//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] 3f2e5a50c34b69ec9f1ef3400900c4a7c26d623e 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: 35 minutes 20 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-2614
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



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

[jira] [Commented] (ZOOKEEPER-1576) Zookeeper cluster - failed to connect to cluster if one of the provided IPs causes java.net.UnknownHostException

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-1576:
--

+1 overall.  GitHub Pull Request  Build
  

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

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

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

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

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

This message is automatically generated.

> Zookeeper cluster - failed to connect to cluster if one of the provided IPs 
> causes java.net.UnknownHostException
> 
>
> Key: ZOOKEEPER-1576
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1576
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.0
> Environment: Three 3.4.3 zookeeper servers in cluster, linux.
>Reporter: Tally Tsabary
>Assignee: Edward Ribeiro
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1576-3.4.patch, ZOOKEEPER-1576.3.patch, 
> ZOOKEEPER-1576.4.patch, ZOOKEEPER-1576.5.patch, ZOOKEEPER-1576.patch
>
>
> Using a cluster of three 3.4.3 zookeeper servers.
> All the servers are up, but on the client machine, the firewall is blocking 
> one of the  servers.
> The following exception is happening, and the client is not connected to any 
> of the other cluster members.
> The exception:Nov 02, 2012 9:54:32 PM 
> com.netflix.curator.framework.imps.CuratorFrameworkImpl logError
> SEVERE: Background exception was not retry-able or retry gave up
> java.net.UnknownHostException: scnrmq003.myworkday.com
> at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
> at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source)
> at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
> at java.net.InetAddress.getAllByName0(Unknown Source)
> at java.net.InetAddress.getAllByName(Unknown Source)
> at java.net.InetAddress.getAllByName(Unknown Source)
> at 
> org.apache.zookeeper.client.StaticHostProvider.(StaticHostProvider.java:60)
> at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:440)
> at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:375)
> The code at the 
> org.apache.zookeeper.client.StaticHostProvider.(StaticHostProvider.java:60)
>  is :
> public StaticHostProvider(Collection serverAddresses) 
> throws UnknownHostException {
> for (InetSocketAddress address : serverAddresses) {
> InetAddress resolvedAddresses[] = InetAddress.getAllByName(address
> .getHostName());
> for (InetAddress resolvedAddress : resolvedAddresses) { 
> this.serverAddresses.add(new InetSocketAddress(resolvedAddress 
> .getHostAddress(), address.getPort())); }
> }
> ..
> The for-loop is not trying to resolve the rest of the servers on the list if 
> there is an UnknownHostException at the 
> InetAddress.getAllByName(address.getHostName()); 
> and it fails the client connection creation.
> I was expecting the connection will be created for the other members of the 
> cluster. 
> Also, InetAddress is a blocking command, and if it takes very long time,  
> (longer than the defined timeout) - that also should allow us to continue to 
> try and connect to the other servers on the list.
> Assuming this will be fixed, and we will get connection to the current 
> available servers, I think the zookeeper should continue to retry to connect 
> to the not-connected server of the cluster, so it will be able to use it 
> later when it is back.
> If one of the servers on the list is not available during the connection 
> creation, then it should be retried every x time despite the fact that we 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2859) CMake build doesn't support OS X

[ASF GitHub Bot (JIRA)]

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

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

Github user andschwa commented on the issue:

https://github.com/apache/zookeeper/pull/319
  
Also, I'd like to test `Autotools` on OS X, because I believe it has the 
same problem (unconditionally adds `libm` and `librt`), but I can't get past 
`autoconf -if` since I don't have `cppunit.m4`. I'm looking high and low for 
it: it's not in `/usr/local/` nor `/opt`, the brew CppUnit didn't come with it, 
and none of the Autotools directories has it. I found 
[ZOOKEEPER-1454](https://issues.apache.org/jira/browse/ZOOKEEPER-1454), and it 
showed me how to specify where `cppunit.m4` is, but that's not much use if I 
don't have it.

Do you know, does anyone have this building on OS X?


> CMake build doesn't support OS X
> 
>
> Key: ZOOKEEPER-2859
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2859
> Project: ZooKeeper
>  Issue Type: Bug
> Environment: OS X 10.12.6
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> Couple problems:
> libm, librt, and libdl are all Linux specific, and provided "for free" on OS X
> CppUnit (at least on OS X) needs `-std=c++11`
> clang's ld doesn't understand --wrap
> I can post an easy patch that at least lets you build the client (but not the 
> tests). The tests use that `--wrap` and it's non trivial to fix that on OS X.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper issue #319: ZOOKEEPER-2859: Fix CMake build on OS X.

[andschwa]

Github user andschwa commented on the issue:

https://github.com/apache/zookeeper/pull/319
  
Also, I'd like to test `Autotools` on OS X, because I believe it has the 
same problem (unconditionally adds `libm` and `librt`), but I can't get past 
`autoconf -if` since I don't have `cppunit.m4`. I'm looking high and low for 
it: it's not in `/usr/local/` nor `/opt`, the brew CppUnit didn't come with it, 
and none of the Autotools directories has it. I found 
[ZOOKEEPER-1454](https://issues.apache.org/jira/browse/ZOOKEEPER-1454), and it 
showed me how to specify where `cppunit.m4` is, but that's not much use if I 
don't have it.

Do you know, does anyone have this building on OS X?


---
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-2859) CMake build doesn't support OS X

[ASF GitHub Bot (JIRA)]

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

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

Github user andschwa commented on the issue:

https://github.com/apache/zookeeper/pull/319
  
@hanm That's bizzare. The 
[log](https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/906/artifact/patchprocess/patchJavadocWarnings.txt/*view*/)
 it provides says this:

```

build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153: 
warning - Tag @link:illegal character: "58" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "45" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link: reference not found: 
https://issues.apache.org/jira/browse/ZOOKEEPER-1355
```

And that issue it's referencing is 
[ancient](https://issues.apache.org/jira/browse/ZOOKEEPER-1355). 

That really is weird.


> CMake build doesn't support OS X
> 
>
> Key: ZOOKEEPER-2859
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2859
> Project: ZooKeeper
>  Issue Type: Bug
> Environment: OS X 10.12.6
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> Couple problems:
> libm, librt, and libdl are all Linux specific, and provided "for free" on OS X
> CppUnit (at least on OS X) needs `-std=c++11`
> clang's ld doesn't understand --wrap
> I can post an easy patch that at least lets you build the client (but not the 
> tests). The tests use that `--wrap` and it's non trivial to fix that on OS X.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper issue #319: ZOOKEEPER-2859: Fix CMake build on OS X.

[andschwa]

Github user andschwa commented on the issue:

https://github.com/apache/zookeeper/pull/319
  
@hanm That's bizzare. The 
[log](https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/906/artifact/patchprocess/patchJavadocWarnings.txt/*view*/)
 it provides says this:

```

build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153: 
warning - Tag @link:illegal character: "58" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "47" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link:illegal character: "45" in 
"https://issues.apache.org/jira/browse/ZOOKEEPER-1355";
  [javadoc] 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build@2/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java:153:
 warning - Tag @link: reference not found: 
https://issues.apache.org/jira/browse/ZOOKEEPER-1355
```

And that issue it's referencing is 
[ancient](https://issues.apache.org/jira/browse/ZOOKEEPER-1355). 

That really is weird.


---
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 #319: ZOOKEEPER-2859: Fix CMake build on OS X.

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/319
  
Any idea why precommit job generates java doc warnings? Seems not related 
to the patch.


---
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-2859) CMake build doesn't support OS X

[ASF GitHub Bot (JIRA)]

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

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

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/319
  
Any idea why precommit job generates java doc warnings? Seems not related 
to the patch.


> CMake build doesn't support OS X
> 
>
> Key: ZOOKEEPER-2859
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2859
> Project: ZooKeeper
>  Issue Type: Bug
> Environment: OS X 10.12.6
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> Couple problems:
> libm, librt, and libdl are all Linux specific, and provided "for free" on OS X
> CppUnit (at least on OS X) needs `-std=c++11`
> clang's ld doesn't understand --wrap
> I can post an easy patch that at least lets you build the client (but not the 
> tests). The tests use that `--wrap` and it's non trivial to fix that on OS X.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-1669) Operations to server will be timed-out while thousands of sessions expired same time

[ASF GitHub Bot (JIRA)]

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

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

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/312
  
3.5 and master already has sessionMap so the issue this PR attempts to fix 
should not be a problem. 
The problem in 3.5 and master is NettyServerCnx and NIOServerCnx has a 
little bit of mismatch which should be fixed in a separate JIRA. 
So let's scope this PR for 3.4 only.


> Operations to server will be timed-out while thousands of sessions expired 
> same time
> 
>
> Key: ZOOKEEPER-1669
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1669
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.5
>Reporter: tokoot
>Assignee: Cheney Sun
>  Labels: performance
>
> If there are thousands of clients, and most of them disconnect with server 
> same time(client restarted or servers partitioned with clients), the server 
> will busy to close those "connections" and become unavailable. The problem is 
> in following:
>   private void closeSessionWithoutWakeup(long sessionId) {
>   HashSet cnxns;
>   synchronized (this.cnxns) {
>   cnxns = (HashSet)this.cnxns.clone();  // other 
> thread will block because of here
>   }
>   ...
>   }
> A real world example that demonstrated this problem (Kudos to [~sun.cheney]):
> {noformat}
> The issue is raised while tens thousands of clients try to reconnect 
> ZooKeeper service. 
> Actually, we came across the issue during maintaining our HBase cluster, 
> which used a 5-server ZooKeeper cluster. 
> The HBase cluster was composed of many many regionservers (in thousand order 
> of magnitude), 
> and connected by tens thousands of clients to do massive reads/writes. 
> Because the r/w throughput is very high, ZooKeeper zxid increased quickly as 
> well. 
> Basically, each two or three weeks, Zookeeper would make leader relection 
> triggered by the zxid roll over. 
> The leader relection will cause the clients(HBase regionservers and HBase 
> clients) disconnected 
> and reconnected with Zookeeper servers in the mean time, and try to renew the 
> sessions.
> In current implementation of session renew, NIOServerCnxnFactory will clone 
> all the connections at first 
> in order to avoid race condition in multi-threads and go iterate the cloned 
> connection set one by one to 
> find the related session to renew. It's very time consuming. In our case 
> (described above), 
> it caused many region servers can't successfully renew session before session 
> timeout, 
> and eventually the HBase cluster lose these region servers and affect the 
> HBase stability.
> The change is to make refactoring to the close session logic and introduce a 
> ConcurrentHashMap 
> to store session id and connection map relation, which is a thread-safe data 
> structure 
> and eliminate the necessary to clone the connection set at first.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper issue #312: ZOOKEEPER-1669: Operations to server will be timed-out...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/312
  
3.5 and master already has sessionMap so the issue this PR attempts to fix 
should not be a problem. 
The problem in 3.5 and master is NettyServerCnx and NIOServerCnx has a 
little bit of mismatch which should be fixed in a separate JIRA. 
So let's scope this PR for 3.4 only.


---
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-2614) Port ZOOKEEPER-1576 to branch3.4

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/zookeeper/pull/320#discussion_r130246293
  
--- Diff: src/java/main/org/apache/zookeeper/client/StaticHostProvider.java 
---
@@ -52,34 +52,36 @@
  * 
  * @param serverAddresses
  *possibly unresolved ZooKeeper server addresses
- * @throws UnknownHostException
  * @throws IllegalArgumentException
  * if serverAddresses is empty or resolves to an empty list
  */
-public StaticHostProvider(Collection 
serverAddresses)
-throws UnknownHostException {
+public StaticHostProvider(Collection 
serverAddresses) {
 for (InetSocketAddress address : serverAddresses) {
-InetAddress ia = address.getAddress();
-InetAddress resolvedAddresses[] = 
InetAddress.getAllByName((ia!=null) ? ia.getHostAddress():
-address.getHostName());
-for (InetAddress resolvedAddress : resolvedAddresses) {
-// If hostName is null but the address is not, we can tell 
that
-// the hostName is an literal IP address. Then we can set 
the host string as the hostname
-// safely to avoid reverse DNS lookup.
-// As far as i know, the only way to check if the hostName 
is null is use toString().
-// Both the two implementations of InetAddress are final 
class, so we can trust the return value of
-// the toString() method.
-if (resolvedAddress.toString().startsWith("/") 
-&& resolvedAddress.getAddress() != null) {
-this.serverAddresses.add(
-new InetSocketAddress(InetAddress.getByAddress(
-address.getHostName(),
-resolvedAddress.getAddress()), 
-address.getPort()));
-} else {
-this.serverAddresses.add(new 
InetSocketAddress(resolvedAddress.getHostAddress(), address.getPort()));
-}  
-}
+   try {
--- End diff --

Indentation here is a little bit off. 4 spaces instead of 8. Please update. 
Other than this patch looks good.


> Port ZOOKEEPER-1576 to branch3.4
> 
>
> Key: ZOOKEEPER-2614
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2614
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.9
>Reporter: Vishal Khandelwal
>Assignee: Vishal Khandelwal
> Fix For: 3.4.11
>
> Attachments: ZOOKEEPER-2614.branch-3.4.00.patch
>
>
> ZOOKEEPER-1576 handles UnknownHostException and it good to have this change 
> for 3.4 branch as well. Porting the changes to 3.4 after resolving the 
> conflicts



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #320: ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3....

[hanm]

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

https://github.com/apache/zookeeper/pull/320#discussion_r130246293
  
--- Diff: src/java/main/org/apache/zookeeper/client/StaticHostProvider.java 
---
@@ -52,34 +52,36 @@
  * 
  * @param serverAddresses
  *possibly unresolved ZooKeeper server addresses
- * @throws UnknownHostException
  * @throws IllegalArgumentException
  * if serverAddresses is empty or resolves to an empty list
  */
-public StaticHostProvider(Collection 
serverAddresses)
-throws UnknownHostException {
+public StaticHostProvider(Collection 
serverAddresses) {
 for (InetSocketAddress address : serverAddresses) {
-InetAddress ia = address.getAddress();
-InetAddress resolvedAddresses[] = 
InetAddress.getAllByName((ia!=null) ? ia.getHostAddress():
-address.getHostName());
-for (InetAddress resolvedAddress : resolvedAddresses) {
-// If hostName is null but the address is not, we can tell 
that
-// the hostName is an literal IP address. Then we can set 
the host string as the hostname
-// safely to avoid reverse DNS lookup.
-// As far as i know, the only way to check if the hostName 
is null is use toString().
-// Both the two implementations of InetAddress are final 
class, so we can trust the return value of
-// the toString() method.
-if (resolvedAddress.toString().startsWith("/") 
-&& resolvedAddress.getAddress() != null) {
-this.serverAddresses.add(
-new InetSocketAddress(InetAddress.getByAddress(
-address.getHostName(),
-resolvedAddress.getAddress()), 
-address.getPort()));
-} else {
-this.serverAddresses.add(new 
InetSocketAddress(resolvedAddress.getHostAddress(), address.getPort()));
-}  
-}
+   try {
--- End diff --

Indentation here is a little bit off. 4 spaces instead of 8. Please update. 
Other than this patch looks good.


---
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-1669) Operations to server will be timed-out while thousands of sessions expired same time

[ASF GitHub Bot (JIRA)]

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

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

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/312
  
@CheneySun I see this patch doesn't apply to `branch-3.5/master` so make 
sure you open another PR to address it on those branches. 👍 


> Operations to server will be timed-out while thousands of sessions expired 
> same time
> 
>
> Key: ZOOKEEPER-1669
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1669
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.5
>Reporter: tokoot
>Assignee: Cheney Sun
>  Labels: performance
>
> If there are thousands of clients, and most of them disconnect with server 
> same time(client restarted or servers partitioned with clients), the server 
> will busy to close those "connections" and become unavailable. The problem is 
> in following:
>   private void closeSessionWithoutWakeup(long sessionId) {
>   HashSet cnxns;
>   synchronized (this.cnxns) {
>   cnxns = (HashSet)this.cnxns.clone();  // other 
> thread will block because of here
>   }
>   ...
>   }
> A real world example that demonstrated this problem (Kudos to [~sun.cheney]):
> {noformat}
> The issue is raised while tens thousands of clients try to reconnect 
> ZooKeeper service. 
> Actually, we came across the issue during maintaining our HBase cluster, 
> which used a 5-server ZooKeeper cluster. 
> The HBase cluster was composed of many many regionservers (in thousand order 
> of magnitude), 
> and connected by tens thousands of clients to do massive reads/writes. 
> Because the r/w throughput is very high, ZooKeeper zxid increased quickly as 
> well. 
> Basically, each two or three weeks, Zookeeper would make leader relection 
> triggered by the zxid roll over. 
> The leader relection will cause the clients(HBase regionservers and HBase 
> clients) disconnected 
> and reconnected with Zookeeper servers in the mean time, and try to renew the 
> sessions.
> In current implementation of session renew, NIOServerCnxnFactory will clone 
> all the connections at first 
> in order to avoid race condition in multi-threads and go iterate the cloned 
> connection set one by one to 
> find the related session to renew. It's very time consuming. In our case 
> (described above), 
> it caused many region servers can't successfully renew session before session 
> timeout, 
> and eventually the HBase cluster lose these region servers and affect the 
> HBase stability.
> The change is to make refactoring to the close session logic and introduce a 
> ConcurrentHashMap 
> to store session id and connection map relation, which is a thread-safe data 
> structure 
> and eliminate the necessary to clone the connection set at first.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper issue #312: ZOOKEEPER-1669: Operations to server will be timed-out...

[eribeiro]

Github user eribeiro commented on the issue:

https://github.com/apache/zookeeper/pull/312
  
@CheneySun I see this patch doesn't apply to `branch-3.5/master` so make 
sure you open another PR to address it on those branches. 👍 


---
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-1669) Operations to server will be timed-out while thousands of sessions expired same time

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/zookeeper/pull/312#discussion_r130229571
  
--- Diff: src/java/main/org/apache/zookeeper/server/ServerCnxn.java ---
@@ -101,6 +102,13 @@ public boolean removeAuthInfo(Id id) {
 
 abstract void setSessionTimeout(int sessionTimeout);
 
+/**
+ * Wrapper method to return the socket address
+ */
+public InetAddress getSocketAddress() {
--- End diff --

`public abstract InetAddress getSocketAddress();`


> Operations to server will be timed-out while thousands of sessions expired 
> same time
> 
>
> Key: ZOOKEEPER-1669
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1669
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.5
>Reporter: tokoot
>Assignee: Cheney Sun
>  Labels: performance
>
> If there are thousands of clients, and most of them disconnect with server 
> same time(client restarted or servers partitioned with clients), the server 
> will busy to close those "connections" and become unavailable. The problem is 
> in following:
>   private void closeSessionWithoutWakeup(long sessionId) {
>   HashSet cnxns;
>   synchronized (this.cnxns) {
>   cnxns = (HashSet)this.cnxns.clone();  // other 
> thread will block because of here
>   }
>   ...
>   }
> A real world example that demonstrated this problem (Kudos to [~sun.cheney]):
> {noformat}
> The issue is raised while tens thousands of clients try to reconnect 
> ZooKeeper service. 
> Actually, we came across the issue during maintaining our HBase cluster, 
> which used a 5-server ZooKeeper cluster. 
> The HBase cluster was composed of many many regionservers (in thousand order 
> of magnitude), 
> and connected by tens thousands of clients to do massive reads/writes. 
> Because the r/w throughput is very high, ZooKeeper zxid increased quickly as 
> well. 
> Basically, each two or three weeks, Zookeeper would make leader relection 
> triggered by the zxid roll over. 
> The leader relection will cause the clients(HBase regionservers and HBase 
> clients) disconnected 
> and reconnected with Zookeeper servers in the mean time, and try to renew the 
> sessions.
> In current implementation of session renew, NIOServerCnxnFactory will clone 
> all the connections at first 
> in order to avoid race condition in multi-threads and go iterate the cloned 
> connection set one by one to 
> find the related session to renew. It's very time consuming. In our case 
> (described above), 
> it caused many region servers can't successfully renew session before session 
> timeout, 
> and eventually the HBase cluster lose these region servers and affect the 
> HBase stability.
> The change is to make refactoring to the close session logic and introduce a 
> ConcurrentHashMap 
> to store session id and connection map relation, which is a thread-safe data 
> structure 
> and eliminate the necessary to clone the connection set at first.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #312: ZOOKEEPER-1669: Operations to server will be ti...

[eribeiro]

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

https://github.com/apache/zookeeper/pull/312#discussion_r130229571
  
--- Diff: src/java/main/org/apache/zookeeper/server/ServerCnxn.java ---
@@ -101,6 +102,13 @@ public boolean removeAuthInfo(Id id) {
 
 abstract void setSessionTimeout(int sessionTimeout);
 
+/**
+ * Wrapper method to return the socket address
+ */
+public InetAddress getSocketAddress() {
--- End diff --

`public abstract InetAddress getSocketAddress();`


---
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_branch35_jdk8 - Build # 619 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.57 MB...]
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:21994
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[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:1149)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit] at java.lang.Thread.run(Thread.java:748)
[junit] 2017-07-30 12:56:21,824 [myid:] - INFO  [New I/O boss 
#18:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-07-30 12:56:21,824 [myid:127.0.0.1:21994] - INFO  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x106d95a28bc is lost, closing socket connection and attempting 
reconnect
[junit] 2017-07-30 12:56:21,964 [myid:127.0.0.1:22120] - INFO  
[main-SendThread(127.0.0.1:22120):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22120. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-07-30 12:56:21,965 [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:22120
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[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:1149)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit] at java.lang.Thread.run(Thread.java:748)
[junit] 2017-07-30 12:56:21,965 [myid:] - WARN  [New I/O boss 
#2772:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x329db815] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:22120
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:22120
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[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:1149)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit] at java.lang.Thread.run(Thread.java:748)
[junit] 2017-07-30 12:56:21,965 [myid:] 

ZooKeeper-trunk-jdk8 - Build # 1147 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 65.08 MB...]
[junit] 2017-07-30 12:44:33,935 [myid:127.0.0.1:22043] - WARN  
[main-SendThread(127.0.0.1:22043):ClientCnxn$SendThread@1235] - Session 
0x1050cf27fef0001 for server 127.0.0.1/127.0.0.1:22043, 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-07-30 12:44:33,972 [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-07-30 12:44:33,972 [myid:127.0.0.1:22117] - WARN  
[main-SendThread(127.0.0.1:22117):ClientCnxn$SendThread@1235] - Session 
0x1050cf52411 for server 127.0.0.1/127.0.0.1:22117, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-07-30 12:44:34,088 [myid:] - INFO  [ProcessThread(sid:0 
cport:22240)::PrepRequestProcessor@614] - Processed session termination for 
sessionid: 0x1050cf84c89
[junit] 2017-07-30 12:44:34,091 [myid:] - INFO  [main:ZooKeeper@1332] - 
Session: 0x1050cf84c89 closed
[junit] 2017-07-30 12:44:34,091 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22240,name1=Connections,name2=127.0.0.1,name3=0x1050cf84c89]
[junit] 2017-07-30 12:44:34,091 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1050cf84c89
[junit] 2017-07-30 12:44:34,092 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 165022
[junit] 2017-07-30 12:44:34,092 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 863
[junit] 2017-07-30 12:44:34,092 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-07-30 12:44:34,092 [myid:] - INFO  [main:ClientBase@601] - 
tearDown starting
[junit] 2017-07-30 12:44:34,092 [myid:] - INFO  [main:ClientBase@571] - 
STOPPING server
[junit] 2017-07-30 12:44:34,093 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:22240
[junit] 2017-07-30 12:44:34,095 [myid:] - INFO  [main:ZooKeeperServer@541] 
- shutting down
[junit] 2017-07-30 12:44:34,095 [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-07-30 12:44:34,095 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-07-30 12:44:34,095 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-07-30 12:44:34,095 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-07-30 12:44:34,095 [myid:] - INFO  [ProcessThread(sid:0 
cport:22240)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop!
[junit] 2017-07-30 12:44:34,096 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-07-30 12:44:34,096 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-07-30 12:44:34,096 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22240,name1=InMemoryDataTree]
[junit] 2017-07-30 12:44:34,096 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port22240]
[junit] 2017-07-30 12:44:34,097 [myid:] - INFO  
[main:FourLetterWordMain@87] - connecting to 127.0.0.1 22240
[junit] 2017-07-30 12:44:34,097 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-07-30 12:44:34,101 [myid:] - INFO  [main:ClientBase@626] - 
fdcount after test is: 2564 at start it was 2564
[junit] 2017-07-30 12:44:34,101 [myid:] - INFO 

Success: ZOOKEEPER- PreCommit Build #908

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34.31 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 3 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 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/908//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/908//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/908//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] 3709ce78b13408326290bed1864ece693427b915 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: 35 minutes 54 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-2614
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



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

[jira] [Commented] (ZOOKEEPER-1576) Zookeeper cluster - failed to connect to cluster if one of the provided IPs causes java.net.UnknownHostException

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-1576:
--

+1 overall.  GitHub Pull Request  Build
  

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

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

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

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

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

This message is automatically generated.

> Zookeeper cluster - failed to connect to cluster if one of the provided IPs 
> causes java.net.UnknownHostException
> 
>
> Key: ZOOKEEPER-1576
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1576
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.0
> Environment: Three 3.4.3 zookeeper servers in cluster, linux.
>Reporter: Tally Tsabary
>Assignee: Edward Ribeiro
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1576-3.4.patch, ZOOKEEPER-1576.3.patch, 
> ZOOKEEPER-1576.4.patch, ZOOKEEPER-1576.5.patch, ZOOKEEPER-1576.patch
>
>
> Using a cluster of three 3.4.3 zookeeper servers.
> All the servers are up, but on the client machine, the firewall is blocking 
> one of the  servers.
> The following exception is happening, and the client is not connected to any 
> of the other cluster members.
> The exception:Nov 02, 2012 9:54:32 PM 
> com.netflix.curator.framework.imps.CuratorFrameworkImpl logError
> SEVERE: Background exception was not retry-able or retry gave up
> java.net.UnknownHostException: scnrmq003.myworkday.com
> at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
> at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source)
> at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
> at java.net.InetAddress.getAllByName0(Unknown Source)
> at java.net.InetAddress.getAllByName(Unknown Source)
> at java.net.InetAddress.getAllByName(Unknown Source)
> at 
> org.apache.zookeeper.client.StaticHostProvider.(StaticHostProvider.java:60)
> at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:440)
> at org.apache.zookeeper.ZooKeeper.(ZooKeeper.java:375)
> The code at the 
> org.apache.zookeeper.client.StaticHostProvider.(StaticHostProvider.java:60)
>  is :
> public StaticHostProvider(Collection serverAddresses) 
> throws UnknownHostException {
> for (InetSocketAddress address : serverAddresses) {
> InetAddress resolvedAddresses[] = InetAddress.getAllByName(address
> .getHostName());
> for (InetAddress resolvedAddress : resolvedAddresses) { 
> this.serverAddresses.add(new InetSocketAddress(resolvedAddress 
> .getHostAddress(), address.getPort())); }
> }
> ..
> The for-loop is not trying to resolve the rest of the servers on the list if 
> there is an UnknownHostException at the 
> InetAddress.getAllByName(address.getHostName()); 
> and it fails the client connection creation.
> I was expecting the connection will be created for the other members of the 
> cluster. 
> Also, InetAddress is a blocking command, and if it takes very long time,  
> (longer than the defined timeout) - that also should allow us to continue to 
> try and connect to the other servers on the list.
> Assuming this will be fixed, and we will get connection to the current 
> available servers, I think the zookeeper should continue to retry to connect 
> to the not-connected server of the cluster, so it will be able to use it 
> later when it is back.
> If one of the servers on the list is not available during the connection 
> creation, then it should be retried every x time despite the fact that we 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ZOOKEEPER-2614) Port ZOOKEEPER-1576 to branch3.4

[ASF GitHub Bot (JIRA)]

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

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

GitHub user tschuettel opened a pull request:

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

ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4

This is a backport of ZOOKEEPER-1576 to the 3.4-line.
When running Zookeeper as an ensemble in a dynamic environment such as
Kubernetes, the DNS entry of a Zookeeper pod is apparently instantly
purged as one of the nodes goes down. This leads to an UnknownHostException
when interacting with the cluster, even though a healthy majority of nodes
is still working.
This behavior is also observed in a firewall situation as described in
ZOOOKEEPER-1576.
This fix catches and logs the UnkownHostException and continues trying the
next node.
Thanks to Vishal Khandelwal for providing the patch.

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

$ git pull https://github.com/DaimlerTSS/zookeeper ZOOKEEPER-2614

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

https://github.com/apache/zookeeper/pull/320.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 #320


commit 67eff1c9984c0081cd36d4f978fcce642362b4b3
Author: Thomas Schüttel 
Date:   2017-07-30T10:50:23Z

ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4

This is a backport of ZOOKEEPER-1576 to the 3.4-line.
When running Zookeeper as an ensemble in a dynamic environment such as
Kubernetes, the DNS entry of a Zookeeper pod is apparently instantly
purged as one of the nodes goes down. This leads to an UnknownHostException
when interacting with the cluster, even though a healthy majority of nodes
is still working.
This behavior is also observed in a firewall situation as described in
ZOOOKEEPER-1576.
This fix catches and logs the UnkownHostException and continues trying the
next node.
Thanks to Vishal Khandelwal for providing the patch.




> Port ZOOKEEPER-1576 to branch3.4
> 
>
> Key: ZOOKEEPER-2614
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2614
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.9
>Reporter: Vishal Khandelwal
>Assignee: Vishal Khandelwal
> Fix For: 3.4.11
>
> Attachments: ZOOKEEPER-2614.branch-3.4.00.patch
>
>
> ZOOKEEPER-1576 handles UnknownHostException and it good to have this change 
> for 3.4 branch as well. Porting the changes to 3.4 after resolving the 
> conflicts



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] zookeeper pull request #320: ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3....

[tschuettel]

GitHub user tschuettel opened a pull request:

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

ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4

This is a backport of ZOOKEEPER-1576 to the 3.4-line.
When running Zookeeper as an ensemble in a dynamic environment such as
Kubernetes, the DNS entry of a Zookeeper pod is apparently instantly
purged as one of the nodes goes down. This leads to an UnknownHostException
when interacting with the cluster, even though a healthy majority of nodes
is still working.
This behavior is also observed in a firewall situation as described in
ZOOOKEEPER-1576.
This fix catches and logs the UnkownHostException and continues trying the
next node.
Thanks to Vishal Khandelwal for providing the patch.

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

$ git pull https://github.com/DaimlerTSS/zookeeper ZOOKEEPER-2614

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

https://github.com/apache/zookeeper/pull/320.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 #320


commit 67eff1c9984c0081cd36d4f978fcce642362b4b3
Author: Thomas Schüttel 
Date:   2017-07-30T10:50:23Z

ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4

This is a backport of ZOOKEEPER-1576 to the 3.4-line.
When running Zookeeper as an ensemble in a dynamic environment such as
Kubernetes, the DNS entry of a Zookeeper pod is apparently instantly
purged as one of the nodes goes down. This leads to an UnknownHostException
when interacting with the cluster, even though a healthy majority of nodes
is still working.
This behavior is also observed in a firewall situation as described in
ZOOOKEEPER-1576.
This fix catches and logs the UnkownHostException and continues trying the
next node.
Thanks to Vishal Khandelwal for providing the patch.




---
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_branch35_openjdk7 - Build # 619 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 67.67 MB...]
[junit] 2017-07-30 10:49:17,246 [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-07-30 10:49:17,246 [myid:127.0.0.1:13915] - WARN  
[main-SendThread(127.0.0.1:13915):ClientCnxn$SendThread@1235] - Session 
0x105bcfb5f55 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:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-07-30 10:49:17,351 [myid:127.0.0.1:13979] - INFO  
[main-SendThread(127.0.0.1:13979):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:13979. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-07-30 10:49:17,352 [myid:127.0.0.1:13979] - WARN  
[main-SendThread(127.0.0.1:13979):ClientCnxn$SendThread@1235] - Session 
0x105bcfbfee7 for server 127.0.0.1/127.0.0.1:13979, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-07-30 10:49:17,495 [myid:127.0.0.1:14038] - INFO  
[main-SendThread(127.0.0.1:14038):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:14038. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-07-30 10:49:17,496 [myid:127.0.0.1:14038] - WARN  
[main-SendThread(127.0.0.1:14038):ClientCnxn$SendThread@1235] - Session 
0x105bcfe3237 for server 127.0.0.1/127.0.0.1:14038, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-07-30 10:49:17,687 [myid:] - INFO  [ProcessThread(sid:0 
cport:14161)::PrepRequestProcessor@611] - Processed session termination for 
sessionid: 0x105bd016da1
[junit] 2017-07-30 10:49:17,688 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port14161,name1=Connections,name2=127.0.0.1,name3=0x105bd016da1]
[junit] 2017-07-30 10:49:17,688 [myid:] - INFO  [main:ZooKeeper@1334] - 
Session: 0x105bd016da1 closed
[junit] 2017-07-30 10:49:17,688 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x105bd016da1
[junit] 2017-07-30 10:49:17,688 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 221218
[junit] 2017-07-30 10:49:17,689 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2431
[junit] 2017-07-30 10:49:17,689 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-07-30 10:49:17,689 [myid:] - INFO  [main:ClientBase@586] - 
tearDown starting
[junit] 2017-07-30 10:49:17,689 [myid:] - INFO  [main:ClientBase@556] - 
STOPPING server
[junit] 2017-07-30 10:49:17,689 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14161
[junit] 2017-07-30 10:49:17,696 [myid:] - INFO  [main:ZooKeeperServer@541] 
- shutting down
[junit] 2017-07-30 10:49:17,696 [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-07-30 10:49:17,697 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-07-30 10:49:17,697 [myid:] - INFO  
[main:PrepRequestProcessor@1005] - Shutting down
[junit] 2017-07

ZooKeeper_branch35_jdk7 - Build # 1062 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 70.96 MB...]
[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] Tests run: 103, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
445.956 sec, Thread: 6, Class: org.apache.zookeeper.test.NettyNettySuiteTest
[junit] 2017-07-30 09:55:04,778 [myid:] - INFO  [New I/O boss 
#3723:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-07-30 09:55:04,778 [myid:127.0.0.1:24751] - INFO  
[main-SendThread(127.0.0.1:24751):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x0 is lost, closing socket connection and attempting reconnect
[junit] 2017-07-30 09:55:04,792 [myid:127.0.0.1:24736] - INFO  
[main-SendThread(127.0.0.1:24736):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24736. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-07-30 09:55:04,793 [myid:] - INFO  [New I/O boss 
#2533:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:24736
[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-07-30 09:55:04,794 [myid:] - WARN  [New I/O boss 
#2533:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0xa8ff4a1a] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:24736
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:24736
[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-07-30 09:55:04,794 [myid:] - INFO  [New I/O b