[jira] [Commented] (ZOOKEEPER-900) FLE implementation should be improved to use non-blocking sockets

2017-03-28 Thread Atri Sharma (JIRA)

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

Atri Sharma commented on ZOOKEEPER-900:
---

Ping?

> FLE implementation should be improved to use non-blocking sockets
> -
>
> Key: ZOOKEEPER-900
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-900
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Vishal Kher
>Assignee: Martin Kuchta
>Priority: Critical
> Fix For: 3.5.4, 3.6.0
>
> Attachments: ZOOKEEPER-900-part2.patch, ZOOKEEPER-900.patch, 
> ZOOKEEPER-900.patch1, ZOOKEEPER-900.patch2
>
>
> From earlier email exchanges:
> 1. Blocking connects and accepts:
> a) The first problem is in manager.toSend(). This invokes connectOne(), which 
> does a blocking connect. While testing, I changed the code so that 
> connectOne() starts a new thread called AsyncConnct(). AsyncConnect.run() 
> does a socketChannel.connect(). After starting AsyncConnect, connectOne 
> starts a timer. connectOne continues with normal operations if the connection 
> is established before the timer expires, otherwise, when the timer expires it 
> interrupts AsyncConnect() thread and returns. In this way, I can have an 
> upper bound on the amount of time we need to wait for connect to succeed. Of 
> course, this was a quick fix for my testing. Ideally, we should use Selector 
> to do non-blocking connects/accepts. I am planning to do that later once we 
> at least have a quick fix for the problem and consensus from others for the 
> real fix (this problem is big blocker for us). Note that it is OK to do 
> blocking IO in SenderWorker and RecvWorker threads since they block IO to the 
> respective peer.
> b) The blocking IO problem is not just restricted to connectOne(), but also 
> in receiveConnection(). The Listener thread calls receiveConnection() for 
> each incoming connection request. receiveConnection does blocking IO to get 
> peer's info (s.read(msgBuffer)). Worse, it invokes connectOne() back to the 
> peer that had sent the connection request. All of this is happening from the 
> Listener. In short, if a peer fails after initiating a connection, the 
> Listener thread won't be able to accept connections from other peers, because 
> it would be stuck in read() or connetOne(). Also the code has an inherent 
> cycle. initiateConnection() and receiveConnection() will have to be very 
> carefully synchronized otherwise, we could run into deadlocks. This code is 
> going to be difficult to maintain/modify.
> Also see: https://issues.apache.org/jira/browse/ZOOKEEPER-822



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


[VOTE] Apache ZooKeeper release 3.5.3-beta candidate 0

2017-03-28 Thread Michael Han
Hi all,

With heartfelt thanks to many contributors, the RC0 for 3.5.3-beta is ready.

3.5.3-beta is the first beta in the planned 3.5 release line leading up to
a stable 3.5 release. It comprises 76 fixes, improvements, and new
features since
3.5.2-alpha was released on July 20th, 2016.

This release includes important security fix around dynamic reconfigure
API, improvements on test infrastructure, and new features such as TTL
node. The full release notes are available at:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12335444


 Please download, test and vote by April 4th 2017, 23:59 UTC+0. 

Source files:
*https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc0/
*

Maven staging repo:
https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.3-beta/


The tag to be voted upon:
*https://github.com/apache/zookeeper/tree/release-3.5.3-rc0
*

ZooKeeper's KEYS file containing PGP keys we use to sign the release:
http://www.apache.org/dist/zookeeper/KEYS

Should we release this candidate?

-- 
Cheers
Michael.


Re: [VOTE] Apache ZooKeeper release 3.4.10 candidate 1

2017-03-28 Thread Flavio Junqueira
+1, ran tests, checked signature and digests, checked license and notice, ran 
some smoke tests locally.

-Flavio

> On 28 Mar 2017, at 22:44, Michael Han  wrote:
> 
> Yes, I forgot to mention that I did some backward compatible verification
> as well. I was using 3.4.10 client to connect to a 3.5.3 ensemble and it
> works as expected.
> 
> On Tue, Mar 28, 2017 at 2:40 PM, Patrick Hunt  wrote:
> 
>> fwiw I also tried running a 3 and 23 node cluster and it worked fine. 3.4.9
>> client accessing 3.4.10 rc1 ensemble worked fine as well.
>> 
>> Patrick
>> 
>> On Mon, Mar 27, 2017 at 5:04 PM, Patrick Hunt  wrote:
>> 
>>> +1 - xsum/sig verified, RAT ran clean, was able to build and run the
>> tests
>>> successfully (mac).
>>> 
>>> Patrick
>>> 
>>> On Thu, Mar 23, 2017 at 5:40 AM, Rakesh Radhakrishnan <
>> rake...@apache.org>
>>> wrote:
>>> 
 This is the second release candidate for 3.4.10. This candidate fixed
>> the
 MiniKDC authentication test case failures reported in the previous
 candidate.
 
 This is a bug fix release candidate for 3.4.10. It fixes 43 issues,
 including
 security feature QuorumPeer mutual authentication via SASL and other
 potential bugs.
 
 The full release notes are available at:
 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
 ctId=12310801=12338036
 
 *** Please download, test and vote by March 29th 2017, 23:59 UTC+0. ***
 
 Source files:
 http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-1/
 
 Maven staging repo:
 https://repository.apache.org/content/groups/staging/org/apa
 che/zookeeper/zookeeper/3.4.10/
 
 The release candidate tag in git to be voted upon: release-3.4.10-rc1
 https://github.com/apache/zookeeper/tree/release-3.4.10-rc1
 
 ZooKeeper's KEYS file containing PGP keys we use to sign the release:
 http://www.apache.org/dist/zookeeper/KEYS
 
 Should we release this candidate?
 
 
 Rakesh
 
>>> 
>>> 
>> 
> 
> 
> 
> -- 
> Cheers
> Michael.



ZooKeeper_branch35_jdk7 - Build # 907 - Failure

2017-03-28 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/907/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 64.51 MB...]
[junit] 2017-03-28 21:54:41,588 [myid:127.0.0.1:16608] - WARN  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1235] - Session 
0x173431b51 for server 127.0.0.1/127.0.0.1:16608, 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-03-28 21:54:41,654 [myid:127.0.0.1:16608] - INFO  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16608. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-28 21:54:41,654 [myid:127.0.0.1:16608] - WARN  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1235] - Session 
0x173431b510001 for server 127.0.0.1/127.0.0.1:16608, 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-03-28 21:54:42,684 [myid:127.0.0.1:16611] - INFO  
[main-SendThread(127.0.0.1:16611):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16611. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-28 21:54:42,685 [myid:127.0.0.1:16611] - WARN  
[main-SendThread(127.0.0.1:16611):ClientCnxn$SendThread@1235] - Session 
0x10173431e7b0001 for server 127.0.0.1/127.0.0.1:16611, 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-03-28 21:54:42,898 [myid:127.0.0.1:16620] - INFO  
[main-SendThread(127.0.0.1:16620):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16620. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-28 21:54:42,898 [myid:4] - INFO  
[NIOServerCxnFactory.AcceptThread:localhost/127.0.0.1:16620:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:33826
[junit] 2017-03-28 21:54:42,898 [myid:127.0.0.1:16620] - INFO  
[main-SendThread(127.0.0.1:16620):ClientCnxn$SendThread@948] - Socket 
connection established, initiating session, client: /127.0.0.1:33826, server: 
127.0.0.1/127.0.0.1:16620
[junit] 2017-03-28 21:54:42,959 [myid:127.0.0.1:16611] - INFO  
[main-SendThread(127.0.0.1:16611):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16611. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-28 21:54:42,959 [myid:127.0.0.1:16611] - WARN  
[main-SendThread(127.0.0.1:16611):ClientCnxn$SendThread@1235] - Session 
0x10173431e7b for server 127.0.0.1/127.0.0.1:16611, 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-03-28 21:54:43,112 [myid:127.0.0.1:16608] - INFO  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16608. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-28 21:54:43,112 [myid:127.0.0.1:16608] - WARN  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1235] - Session 
0x173431b510001 for server 127.0.0.1/127.0.0.1:16608, unexpected error, closing 
socket connection and attempting reconnect

Re: [VOTE] Apache ZooKeeper release 3.4.10 candidate 1

2017-03-28 Thread Michael Han
Yes, I forgot to mention that I did some backward compatible verification
as well. I was using 3.4.10 client to connect to a 3.5.3 ensemble and it
works as expected.

On Tue, Mar 28, 2017 at 2:40 PM, Patrick Hunt  wrote:

> fwiw I also tried running a 3 and 23 node cluster and it worked fine. 3.4.9
> client accessing 3.4.10 rc1 ensemble worked fine as well.
>
> Patrick
>
> On Mon, Mar 27, 2017 at 5:04 PM, Patrick Hunt  wrote:
>
> > +1 - xsum/sig verified, RAT ran clean, was able to build and run the
> tests
> > successfully (mac).
> >
> > Patrick
> >
> > On Thu, Mar 23, 2017 at 5:40 AM, Rakesh Radhakrishnan <
> rake...@apache.org>
> > wrote:
> >
> >> This is the second release candidate for 3.4.10. This candidate fixed
> the
> >> MiniKDC authentication test case failures reported in the previous
> >> candidate.
> >>
> >> This is a bug fix release candidate for 3.4.10. It fixes 43 issues,
> >> including
> >> security feature QuorumPeer mutual authentication via SASL and other
> >> potential bugs.
> >>
> >> The full release notes are available at:
> >>
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> >> ctId=12310801=12338036
> >>
> >> *** Please download, test and vote by March 29th 2017, 23:59 UTC+0. ***
> >>
> >> Source files:
> >> http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-1/
> >>
> >> Maven staging repo:
> >> https://repository.apache.org/content/groups/staging/org/apa
> >> che/zookeeper/zookeeper/3.4.10/
> >>
> >> The release candidate tag in git to be voted upon: release-3.4.10-rc1
> >> https://github.com/apache/zookeeper/tree/release-3.4.10-rc1
> >>
> >> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> >> http://www.apache.org/dist/zookeeper/KEYS
> >>
> >> Should we release this candidate?
> >>
> >>
> >> Rakesh
> >>
> >
> >
>



-- 
Cheers
Michael.


Re: [VOTE] Apache ZooKeeper release 3.4.10 candidate 1

2017-03-28 Thread Patrick Hunt
fwiw I also tried running a 3 and 23 node cluster and it worked fine. 3.4.9
client accessing 3.4.10 rc1 ensemble worked fine as well.

Patrick

On Mon, Mar 27, 2017 at 5:04 PM, Patrick Hunt  wrote:

> +1 - xsum/sig verified, RAT ran clean, was able to build and run the tests
> successfully (mac).
>
> Patrick
>
> On Thu, Mar 23, 2017 at 5:40 AM, Rakesh Radhakrishnan 
> wrote:
>
>> This is the second release candidate for 3.4.10. This candidate fixed the
>> MiniKDC authentication test case failures reported in the previous
>> candidate.
>>
>> This is a bug fix release candidate for 3.4.10. It fixes 43 issues,
>> including
>> security feature QuorumPeer mutual authentication via SASL and other
>> potential bugs.
>>
>> The full release notes are available at:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12310801=12338036
>>
>> *** Please download, test and vote by March 29th 2017, 23:59 UTC+0. ***
>>
>> Source files:
>> http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-1/
>>
>> Maven staging repo:
>> https://repository.apache.org/content/groups/staging/org/apa
>> che/zookeeper/zookeeper/3.4.10/
>>
>> The release candidate tag in git to be voted upon: release-3.4.10-rc1
>> https://github.com/apache/zookeeper/tree/release-3.4.10-rc1
>>
>> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
>> http://www.apache.org/dist/zookeeper/KEYS
>>
>> Should we release this candidate?
>>
>>
>> Rakesh
>>
>
>


ZooKeeper_branch35_jdk8 - Build # 475 - Failure

2017-03-28 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/475/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 66.26 MB...]
[junit] 2017-03-28 20:59:56,884 [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-03-28 20:59:56,884 [myid:127.0.0.1:30202] - WARN  
[main-SendThread(127.0.0.1:30202):ClientCnxn$SendThread@1235] - Session 
0x3045c838959 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: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-28 20:59:57,424 [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-03-28 20:59:57,425 [myid:127.0.0.1:30199] - WARN  
[main-SendThread(127.0.0.1:30199):ClientCnxn$SendThread@1235] - Session 
0x2045c838d36 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: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-28 20:59:57,857 [myid:127.0.0.1:30073] - INFO  
[main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30073. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-28 20:59:57,858 [myid:127.0.0.1:30073] - WARN  
[main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1235] - Session 
0x1045c7fbd0d for server 127.0.0.1/127.0.0.1:30073, 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-28 20:59:57,888 [myid:] - INFO  [ProcessThread(sid:0 
cport:30319)::PrepRequestProcessor@613] - Processed session termination for 
sessionid: 0x1045c86e498
[junit] 2017-03-28 20:59:57,895 [myid:] - INFO  [main:ZooKeeper@1326] - 
Session: 0x1045c86e498 closed
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1045c86e498
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port30319,name1=Connections,name2=127.0.0.1,name3=0x1045c86e498]
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 116345
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 467
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2017-03-28 20:59:57,896 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:30319
[junit] 2017-03-28 20:59:57,898 [myid:] - INFO  [main:ZooKeeperServer@541] 
- shutting down
[junit] 2017-03-28 20:59:57,898 [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-28 20:59:57,898 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-28 20:59:57,898 [myid:] - INFO  
[main:PrepRequestProcessor@1004] - Shutting down
[junit] 2017-03-28 

Failed: ZOOKEEPER- PreCommit Build #490

2017-03-28 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/490/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 19.33 KB...]
warning: Cannot merge binary files: docs/zookeeperOver.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/zookeeperObservers.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/zookeeperJMX.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/zookeeperInternals.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/zookeeperHierarchicalQuorums.pdf (HEAD 
vs. 8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/zookeeperAdmin.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/recipes.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/linkmap.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/javaExample.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)
warning: Cannot merge binary files: docs/index.pdf (HEAD vs. 
8ce24f9e675cbefffb8f21a47e06b42864475a60)

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1766)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1762)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1409)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$3.execute(CliGitAPIImpl.java:588)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.merge(AbstractGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.merge(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)
at ..remote call to H5(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.$Proxy96.merge(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.merge(RemoteGitImpl.java:435)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:107)
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)
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 

ZooKeeper-trunk-openjdk7 - Build # 1418 - Failure

2017-03-28 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1418/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 62.91 MB...]
[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-28 20:02:13,933 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port11468,name1=Connections,name2=127.0.0.1,name3=0x10341b57622]
[junit] 2017-03-28 20:02:14,033 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x10341b57622 closed
[junit] 2017-03-28 20:02:14,033 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10341b57622
[junit] 2017-03-28 20:02:14,034 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 227151
[junit] 2017-03-28 20:02:14,034 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2426
[junit] 2017-03-28 20:02:14,034 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-28 20:02:14,034 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-03-28 20:02:14,035 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-03-28 20:02:14,035 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:11468
[junit] 2017-03-28 20:02:14,041 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-03-28 20:02:14,041 [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-28 20:02:14,042 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-28 20:02:14,042 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-03-28 20:02:14,046 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-28 20:02:14,046 [myid:] - INFO  [ProcessThread(sid:0 
cport:11468)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-03-28 20:02:14,047 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-28 20:02:14,047 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-28 20:02:14,050 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port11468,name1=InMemoryDataTree]
[junit] 2017-03-28 20:02:14,050 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11468]
[junit] 2017-03-28 20:02:14,054 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11468
[junit] 2017-03-28 20:02:14,054 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-03-28 20:02:14,066 [myid:] - INFO  [main:ClientBase@583] - 
fdcount after test is: 7136 at start it was 7136
[junit] 2017-03-28 20:02:14,066 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-03-28 20:02:14,066 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
464.168 sec, Thread: 1, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-03-28 20:02:14,277 [myid:127.0.0.1:11345] - INFO  
[main-SendThread(127.0.0.1:11345):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:11345. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-28 20:02:14,278 [myid:127.0.0.1:11345] - WARN  
[main-SendThread(127.0.0.1:11345):ClientCnxn$SendThread@1235] - Session 
0x10341b23c2b for server 127.0.0.1/127.0.0.1:11345, 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 

[jira] [Updated] (ZOOKEEPER-2741) A Swift Connector of ZooKeeper is available now: Perfect-ZooKeeper

2017-03-28 Thread Rockford Wei (JIRA)

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

Rockford Wei updated ZOOKEEPER-2741:

Description: 
Perfect-ZooKeeper is a Swift class wrapper of zookeeper C connector:

Source Code:
https://github.com/PerfectlySoft/Perfect-ZooKeeper

Document:
http://www.perfect.org/docs/ZooKeeper.html

Perfect is an open source Server Side Swift framework supported by 
PerfectlySoft Inc. since 2015.

We are happy to share this new components as a community contribution.

  was:
Perfect-ZooKeeper is a Swift class wrapper of zookeeper C connector:

Source Code:
https://github.com/PerfectlySoft/Perfect-ZooKeeper

Document:
http://www.perfect.org/docs/ZooKeeper.html

Perfect is an open source Server Side Swift framework supported by 
PerfectlySoft Inc. since 2015.


> A Swift Connector of ZooKeeper is available now: Perfect-ZooKeeper
> --
>
> Key: ZOOKEEPER-2741
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2741
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: contrib
>Reporter: Rockford Wei
>Priority: Minor
>
> Perfect-ZooKeeper is a Swift class wrapper of zookeeper C connector:
> Source Code:
> https://github.com/PerfectlySoft/Perfect-ZooKeeper
> Document:
> http://www.perfect.org/docs/ZooKeeper.html
> Perfect is an open source Server Side Swift framework supported by 
> PerfectlySoft Inc. since 2015.
> We are happy to share this new components as a community contribution.



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


[jira] [Created] (ZOOKEEPER-2741) A Swift Connector of ZooKeeper is available now: Perfect-ZooKeeper

2017-03-28 Thread Rockford Wei (JIRA)
Rockford Wei created ZOOKEEPER-2741:
---

 Summary: A Swift Connector of ZooKeeper is available now: 
Perfect-ZooKeeper
 Key: ZOOKEEPER-2741
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2741
 Project: ZooKeeper
  Issue Type: New Feature
  Components: contrib
Reporter: Rockford Wei
Priority: Minor


Perfect-ZooKeeper is a Swift class wrapper of zookeeper C connector:

Source Code:
https://github.com/PerfectlySoft/Perfect-ZooKeeper

Document:
http://www.perfect.org/docs/ZooKeeper.html

Perfect is an open source Server Side Swift framework supported by 
PerfectlySoft Inc. since 2015.



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


Re: [VOTE] Apache ZooKeeper release 3.4.10 candidate 1

2017-03-28 Thread Michael Han
+1 (non-binding).

* Download source, verified checksum and signatures.
* Build source successfully on OS X and Ubuntu. Unit tests pass (both Java
and C).
* Deploy a 3 node ensemble. Verified sanity through command line and smoke
test.
* Deploy a 3 node ensemble with Kerberos enabled (ZOOKEEPER-1045), verified
sanity through command line and smoke test.
* Verified 4lw is disabled by default.
* Checked release note, looks good.


On Mon, Mar 27, 2017 at 5:04 PM, Patrick Hunt  wrote:

> +1 - xsum/sig verified, RAT ran clean, was able to build and run the tests
> successfully (mac).
>
> Patrick
>
> On Thu, Mar 23, 2017 at 5:40 AM, Rakesh Radhakrishnan 
> wrote:
>
> > This is the second release candidate for 3.4.10. This candidate fixed the
> > MiniKDC authentication test case failures reported in the previous
> > candidate.
> >
> > This is a bug fix release candidate for 3.4.10. It fixes 43 issues,
> > including
> > security feature QuorumPeer mutual authentication via SASL and other
> > potential bugs.
> >
> > The full release notes are available at:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12310801=12338036
> >
> > *** Please download, test and vote by March 29th 2017, 23:59 UTC+0. ***
> >
> > Source files:
> > http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-1/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/groups/staging/org/
> > apache/zookeeper/zookeeper/3.4.10/
> >
> > The release candidate tag in git to be voted upon: release-3.4.10-rc1
> > https://github.com/apache/zookeeper/tree/release-3.4.10-rc1
> >
> > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/zookeeper/KEYS
> >
> > Should we release this candidate?
> >
> >
> > Rakesh
> >
>



-- 
Cheers
Michael.


[GitHub] zookeeper issue #210: Fix typo

2017-03-28 Thread afine
Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/210
  
@jeffwidman could you please open a jira to track this change: 
https://issues.apache.org/jira/


---
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 #210: Fix typo

2017-03-28 Thread afine
Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/210
  
+1 looks like this typo also exists in branch-3.4 and 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] [Updated] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

2017-03-28 Thread Michael Han (JIRA)

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

Michael Han updated ZOOKEEPER-2722:
---
Fix Version/s: (was: 3.5.3)
   3.5.4

> 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
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky
> Fix For: 3.5.4, 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)


Vote on release 3.4.10 candidate 1

2017-03-28 Thread Rakesh Radhakrishnan
Thank you to the whole community on the effort to get a release candidate
out.

Everyone, please take this opportunity to test and vote on the release
candidate by March 29th 2017, 23:59 UTC+0. It would be really helpful if
multiple folks test with their systems to make sure that the RC is good.

Thanks,
Rakesh

-- Forwarded message --
From: Rakesh Radhakrishnan 
Date: Thu, Mar 23, 2017 at 6:10 PM
Subject: [VOTE] Apache ZooKeeper release 3.4.10 candidate 1
To: DevZooKeeper 


This is the second release candidate for 3.4.10. This candidate fixed the
MiniKDC authentication test case failures reported in the previous
candidate.

This is a bug fix release candidate for 3.4.10. It fixes 43 issues,
including
security feature QuorumPeer mutual authentication via SASL and other
potential bugs.

The full release notes are available at:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12310801=12338036

*** Please download, test and vote by March 29th 2017, 23:59 UTC+0. ***

Source files:
http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-1/

Maven staging repo:
https://repository.apache.org/content/groups/staging/org/
apache/zookeeper/zookeeper/3.4.10/

The release candidate tag in git to be voted upon: release-3.4.10-rc1
https://github.com/apache/zookeeper/tree/release-3.4.10-rc1

ZooKeeper's KEYS file containing PGP keys we use to sign the release:
http://www.apache.org/dist/zookeeper/KEYS

Should we release this candidate?


Rakesh


Re: ZOOKEEPER-900

2017-03-28 Thread Edward Ribeiro
Hi Atri,

Comment on the issues themselves. It helps.

Regards,
Eddie

On Tue, Mar 28, 2017 at 1:33 AM, Atri Sharma  wrote:

> Hi Patrick,
>
> I am fine with either. I tried pinging the owners but got no response.
>
> Please let me know.
>
> Regards,
>
> Atri
>
> On Tue, Mar 28, 2017 at 4:51 AM, Patrick Hunt  wrote:
> > Hi Atri. Which do you intend to work on? 900, 901, or both? Typically if
> > someone is intending to work on something they will be listed as the
> > "assigned" in JIRA. They would be the first person to check in with. If
> > they no longer intend to work on something it's easy enough to reassign.
> >
> > Regards,
> >
> > Patrick
> >
> > On Sat, Mar 25, 2017 at 7:36 AM, Atri Sharma 
> wrote:
> >
> >> Hi folks,
> >>
> >> I was looking to work on ZOOKEEPER-901. Could anybody please let me
> >> know if they are working on it?
> >>
> >> --
> >> Regards,
> >>
> >> Atri
> >> l'apprenant
> >>
>
>
>
> --
> Regards,
>
> Atri
> l'apprenant
>


ZooKeeper_branch35_openjdk7 - Build # 473 - Still Failing

2017-03-28 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/473/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 61.39 MB...]
[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-28 10:07:31,838 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port16854,name1=Connections,name2=127.0.0.1,name3=0x1033f5f092d]
[junit] 2017-03-28 10:07:31,939 [myid:] - INFO  [main:ZooKeeper@1326] - 
Session: 0x1033f5f092d closed
[junit] 2017-03-28 10:07:31,939 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 230784
[junit] 2017-03-28 10:07:31,939 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1033f5f092d
[junit] 2017-03-28 10:07:31,939 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2428
[junit] 2017-03-28 10:07:31,940 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-28 10:07:31,940 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2017-03-28 10:07:31,940 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2017-03-28 10:07:31,940 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:16854
[junit] 2017-03-28 10:07:31,948 [myid:] - INFO  [main:ZooKeeperServer@541] 
- shutting down
[junit] 2017-03-28 10:07:31,948 [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-28 10:07:31,948 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-28 10:07:31,949 [myid:] - INFO  
[main:PrepRequestProcessor@1004] - Shutting down
[junit] 2017-03-28 10:07:31,949 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-28 10:07:31,949 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-28 10:07:31,949 [myid:] - INFO  [ProcessThread(sid:0 
cport:16854)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop!
[junit] 2017-03-28 10:07:31,949 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-28 10:07:31,950 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port16854,name1=InMemoryDataTree]
[junit] 2017-03-28 10:07:31,950 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port16854]
[junit] 2017-03-28 10:07:31,951 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 16854
[junit] 2017-03-28 10:07:31,951 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-03-28 10:07:31,963 [myid:] - INFO  [main:ClientBase@568] - 
fdcount after test is: 7132 at start it was 7132
[junit] 2017-03-28 10:07:31,963 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-03-28 10:07:31,963 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
465.358 sec, Thread: 3, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2017-03-28 10:07:32,245 [myid:] - INFO