date:20161016

ZooKeeper-trunk-solaris - Build # 1349 - Still Failing

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 96518 lines...]
[junit] 2016-10-16 07:38:45,486 [myid:2] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-10-16 07:38:45,487 [myid:2] - INFO  
[NIOServerCxnFactory.AcceptThread:localhost/127.0.0.1:11247:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-10-16 07:38:45,487 [myid:2] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-10-16 07:38:45,486 [myid:2] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-10-16 07:38:45,486 [myid:2] - WARN  
[LearnerHandler-/127.0.0.1:48273:LearnerHandler@619] - *** GOODBYE 
/127.0.0.1:48273 
[junit] 2016-10-16 07:38:45,488 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/127.0.0.1:11247)(secure=disabled):MBeanRegistry@128] 
- Unregister MBean [org.apache.ZooKeeperService:name0=Leader]
[junit] 2016-10-16 07:38:45,488 [myid:2] - INFO  
[localhost/127.0.0.1:11249:QuorumCnxManager$Listener@661] - Leaving listener
[junit] 2016-10-16 07:38:45,488 [myid:2] - WARN  
[QuorumPeer[myid=2](plain=/127.0.0.1:11247)(secure=disabled):QuorumPeer@1127] - 
Unexpected exception
[junit] java.lang.InterruptedException
[junit] at java.lang.Object.wait(Native Method)
[junit] at 
org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:561)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1124)
[junit] 2016-10-16 07:38:45,488 [myid:2] - WARN  
[LearnerHandler-/127.0.0.1:48273:LearnerHandler@903] - Ignoring unexpected 
exception
[junit] java.lang.InterruptedException
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1219)
[junit] at 
java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:340)
[junit] at 
java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:338)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:901)
[junit] at 
org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622)
[junit] 2016-10-16 07:38:45,489 [myid:2] - INFO  
[QuorumPeer[myid=2](plain=/127.0.0.1:11247)(secure=disabled):Leader@623] - 
Shutting down
[junit] 2016-10-16 07:38:45,489 [myid:] - INFO  [main:QuorumBase@398] - 
Shutting down leader election 
QuorumPeer[myid=2](plain=/127.0.0.1:11247)(secure=disabled)
[junit] 2016-10-16 07:38:45,490 [myid:2] - WARN  
[QuorumPeer[myid=2](plain=/127.0.0.1:11247)(secure=disabled):QuorumPeer@1158] - 
PeerState set to LOOKING
[junit] 2016-10-16 07:38:45,490 [myid:] - INFO  [main:QuorumBase@403] - 
Waiting for QuorumPeer[myid=2](plain=/127.0.0.1:11247)(secure=disabled) to exit 
thread
[junit] 2016-10-16 07:38:45,490 [myid:2] - WARN  
[QuorumPeer[myid=2](plain=/127.0.0.1:11247)(secure=disabled):QuorumPeer@1140] - 
QuorumPeer main thread exited
[junit] 2016-10-16 07:38:45,591 [myid:] - INFO  [main:ZooKeeper@1315] - 
Session: 0x22449688033 closed
[junit] 2016-10-16 07:38:45,591 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x22449688033
[junit] 2016-10-16 07:38:45,591 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 13252
[junit] 2016-10-16 07:38:45,591 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 81
[junit] 2016-10-16 07:38:45,591 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testConfigFileBackwardCompatibility
[junit] 2016-10-16 07:38:45,591 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testConfigFileBackwardCompatibility
[junit] 2016-10-16 07:38:45,591 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testConfigFileBackwardCompatibility
[junit] 2016-10-16 07:38:45,981 [myid:2] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection$Messenger$WorkerReceiver@440] - 
WorkerReceiver is down
[junit] 2016-10-16 07:38:46,161 [myid:127.0.0.1:11232] - INFO  
[Time-limited test-SendThread(127.0.0.1:11232):ClientCnxn$SendThread@1113] - 
Opening socket connection to server 127.0.0.1/127.0.0.1:11232. Will not attempt 
to authenticate using SASL (unknown error)
[junit] 2016-10-16 07:38:46,161 [myid:127.0.0.1:11232] - ERROR 
[Time-limited test-SendThread(127.0.0.1:11232):ClientCnxnSocketNIO@287] - 
Unable to open socket to 127.0.0.1/127.0.0.1:11232
[junit] 2016-10-16 07:38:46,161 [myid:127.0.0.1:11232] - WARN  
[Time

ZooKeeper_branch35_openjdk7 - Build # 265 - Still Failing

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 465133 lines...]
[junit] 2016-10-16 10:16:35,142 [myid:127.0.0.1:27431] - WARN  
[main-SendThread(127.0.0.1:27431):ClientCnxn$SendThread@1235] - Session 
0x2001c143e0e for server 127.0.0.1/127.0.0.1:27431, 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] 2016-10-16 10:16:35,320 [myid:127.0.0.1:27434] - INFO  
[main-SendThread(127.0.0.1:27434):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27434. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 10:16:35,320 [myid:127.0.0.1:27434] - WARN  
[main-SendThread(127.0.0.1:27434):ClientCnxn$SendThread@1235] - Session 
0x3001c143e23 for server 127.0.0.1/127.0.0.1:27434, 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] 2016-10-16 10:16:35,561 [myid:127.0.0.1:27428] - INFO  
[main-SendThread(127.0.0.1:27428):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27428. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 10:16:35,562 [myid:127.0.0.1:27428] - WARN  
[main-SendThread(127.0.0.1:27428):ClientCnxn$SendThread@1235] - Session 
0x1001c143e11 for server 127.0.0.1/127.0.0.1:27428, 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] 2016-10-16 10:16:35,997 [myid:127.0.0.1:27458] - INFO  
[main-SendThread(127.0.0.1:27458):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27458. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 10:16:35,998 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:/127.0.0.1:27458:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:59601
[junit] 2016-10-16 10:16:35,998 [myid:127.0.0.1:27458] - INFO  
[main-SendThread(127.0.0.1:27458):ClientCnxn$SendThread@948] - Socket 
connection established, initiating session, client: /127.0.0.1:59601, server: 
127.0.0.1/127.0.0.1:27458
[junit] 2016-10-16 10:16:35,998 [myid:] - WARN  
[NIOWorkerThread-6:NIOServerCnxn@369] - Exception causing close of session 0x0: 
ZooKeeperServer not running
[junit] 2016-10-16 10:16:35,998 [myid:] - INFO  
[NIOWorkerThread-6:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:59601 (no session established for client)
[junit] 2016-10-16 10:16:35,998 [myid:127.0.0.1:27458] - INFO  
[main-SendThread(127.0.0.1:27458):ClientCnxn$SendThread@1231] - Unable to read 
additional data from server sessionid 0x0, likely server has closed socket, 
closing socket connection and attempting reconnect
[junit] 2016-10-16 10:16:36,704 [myid:127.0.0.1:27428] - INFO  
[main-SendThread(127.0.0.1:27428):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27428. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 10:16:36,705 [myid:127.0.0.1:27428] - WARN  
[main-SendThread(127.0.0.1:27428):ClientCnxn$SendThread@1235] - Session 
0x1001c143e11 for server 127.0.0.1/127.0.0.1:27428, 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:3

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

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 462750 lines...]
[junit] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[junit] at java.net.Socket.connect(Socket.java:589)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:441)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:482)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.toSend(QuorumCnxManager.java:419)
[junit] at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.process(FastLeaderElection.java:486)
[junit] at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.run(FastLeaderElection.java:465)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2016-10-16 12:00:53,858 [myid:] - INFO  
[WorkerReceiver[myid=3]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x20003 (n.zxid), 0x3 (n.round), LOOKING 
(n.state), 3 (n.sid), 0x2 (n.peerEPoch), LOOKING (my state)1 (n.config 
version)
[junit] 2016-10-16 12:00:53,858 [myid:] - INFO  
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message 
format version), 3 (n.leader), 0x20003 (n.zxid), 0x3 (n.round), LOOKING 
(n.state), 3 (n.sid), 0x2 (n.peerEPoch), LEADING (my state)1 (n.config 
version)
[junit] 2016-10-16 12:00:53,859 [myid:] - INFO  
[WorkerReceiver[myid=3]:FastLeaderElection@688] - Notification: 2 (message 
format version), 2 (n.leader), 0x0 (n.zxid), 0x (n.round), 
LEADING (n.state), 2 (n.sid), 0x1 (n.peerEPoch), LOOKING (my state)1 
(n.config version)
[junit] Running org.apache.zookeeper.server.ZxidRolloverTest in thread 2
[junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 
sec, Thread: 2, Class: org.apache.zookeeper.server.ZxidRolloverTest
[junit] Test org.apache.zookeeper.server.ZxidRolloverTest FAILED (timeout)
[junit] 2016-10-16 12:02:01,886 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 132335
[junit] 2016-10-16 12:02:01,887 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 55
[junit] 2016-10-16 12:02:01,887 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testManyChildWatchersAutoReset
[junit] 2016-10-16 12:02:01,887 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-16 12:02:01,888 [myid:] - INFO  [ProcessThread(sid:0 
cport:19304)::PrepRequestProcessor@605] - Processed session termination for 
sessionid: 0x1015fcd5b27
[junit] 2016-10-16 12:02:01,908 [myid:] - INFO  [main:ZooKeeper@1315] - 
Session: 0x1015fcd5b27 closed
[junit] 2016-10-16 12:02:01,908 [myid:] - INFO  
[NIOWorkerThread-32:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port19304,name1=Connections,name2=127.0.0.1,name3=0x1015fcd5b27]
[junit] 2016-10-16 12:02:01,908 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1015fcd5b27
[junit] 2016-10-16 12:02:01,908 [myid:] - INFO  [ProcessThread(sid:0 
cport:19304)::PrepRequestProcessor@605] - Processed session termination for 
sessionid: 0x1015fcd5b270001
[junit] 2016-10-16 12:02:01,909 [myid:] - INFO  
[NIOWorkerThread-32:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:34880 which had sessionid 0x1015fcd5b27
[junit] 2016-10-16 12:02:01,936 [myid:] - INFO  [main:ZooKeeper@1315] - 
Session: 0x1015fcd5b270001 closed
[junit] 2016-10-16 12:02:01,936 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1015fcd5b270001
[junit] 2016-10-16 12:02:01,936 [myid:] - INFO  
[NIOWorkerThread-16:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port19304,name1=Connections,name2=127.0.0.1,name3=0x1015fcd5b270001]
[junit] 2016-10-16 12:02:01,936 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-16 12:02:01,937 [myid:] - INFO  
[NIOWorkerThread-16:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:34923 which had sessionid 0x1015fcd5b270001
[junit] 2016-10-16 12:02:01,937 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-10-16 12:02:01,938 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:19304:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-10-16 12:02:01,939 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0

ZooKeeper_branch35_jdk8 - Build # 267 - Failure

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 472337 lines...]
[junit] 2016-10-16 12:22:37,974 [myid:127.0.0.1:24738] - INFO  
[main-SendThread(127.0.0.1:24738):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24738. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 12:22:37,975 [myid:127.0.0.1:24738] - WARN  
[main-SendThread(127.0.0.1:24738):ClientCnxn$SendThread@1235] - Session 
0x20160e86db0 for server 127.0.0.1/127.0.0.1:24738, 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] 2016-10-16 12:22:38,279 [myid:127.0.0.1:24735] - INFO  
[main-SendThread(127.0.0.1:24735):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24735. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 12:22:38,280 [myid:127.0.0.1:24735] - WARN  
[main-SendThread(127.0.0.1:24735):ClientCnxn$SendThread@1235] - Session 
0x10160e86c0e for server 127.0.0.1/127.0.0.1:24735, 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] 2016-10-16 12:22:38,657 [myid:127.0.0.1:24762] - INFO  
[main-SendThread(127.0.0.1:24762):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24762. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 12:22:38,657 [myid:127.0.0.1:24762] - INFO  
[main-SendThread(127.0.0.1:24762):ClientCnxn$SendThread@948] - Socket 
connection established, initiating session, client: /127.0.0.1:40527, server: 
127.0.0.1/127.0.0.1:24762
[junit] 2016-10-16 12:22:38,657 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:/127.0.0.1:24762:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:40527
[junit] 2016-10-16 12:22:38,657 [myid:] - WARN  
[NIOWorkerThread-28:NIOServerCnxn@369] - Exception causing close of session 
0x0: ZooKeeperServer not running
[junit] 2016-10-16 12:22:38,658 [myid:] - INFO  
[NIOWorkerThread-28:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:40527 (no session established for client)
[junit] 2016-10-16 12:22:38,658 [myid:127.0.0.1:24762] - INFO  
[main-SendThread(127.0.0.1:24762):ClientCnxn$SendThread@1231] - Unable to read 
additional data from server sessionid 0x0, likely server has closed socket, 
closing socket connection and attempting reconnect
[junit] 2016-10-16 12:22:38,961 [myid:127.0.0.1:24741] - INFO  
[main-SendThread(127.0.0.1:24741):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24741. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 12:22:38,961 [myid:127.0.0.1:24741] - WARN  
[main-SendThread(127.0.0.1:24741):ClientCnxn$SendThread@1235] - Session 
0x30160e86c0e for server 127.0.0.1/127.0.0.1:24741, 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] 2016-10-16 12:22:39,489 [myid:127.0.0.1:24735] - INFO  
[main-SendThread(127.0.0.1:24735):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24735. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 12:22:39,490 [myid:127.0.0.1:24735] - WARN  
[main-SendThread(127.0.0.1:24735):ClientCnxn$SendThread@1235] - Session 
0x10160e86c0e for server 127.0.0.1/127.0.0.1:24735, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit]

[jira] [Updated] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2467:

Attachment: ZOOKEEPER-2467.patch

> NullPointerException when redo Command is passed negative value
> ---
>
> Key: ZOOKEEPER-2467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.8, 3.5.1, 3.5.2
> Environment: Linux , windows
>Reporter: Joshi Shankar
>Assignee: Rakesh Kumar Singh
>Priority: Minor
> Fix For: 3.4.10, 3.5.1, 3.5.3
>
> Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch
>
>
> When negative value of argument is passed to redo command .
> [zk: localhost:2181(CONNECTED) 0] redo -1
> Exception in thread "main" java.lang.NullPointerException
> at java.util.StringTokenizer.(Unknown Source)
> at java.util.StringTokenizer.(Unknown Source)
> at 
> org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227)
> at 
> org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645)
> at 
> org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588)
> at 
> org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value

2016-10-16 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on ZOOKEEPER-2467:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12833640/ZOOKEEPER-2467.patch
  against trunk revision 422058c222a8a31ec7cfd4113fbdc036181f751d.

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

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

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3491//console

This message is automatically generated.

> NullPointerException when redo Command is passed negative value
> ---
>
> Key: ZOOKEEPER-2467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.8, 3.5.1, 3.5.2
> Environment: Linux , windows
>Reporter: Joshi Shankar
>Assignee: Rakesh Kumar Singh
>Priority: Minor
> Fix For: 3.4.10, 3.5.1, 3.5.3
>
> Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch
>
>
> When negative value of argument is passed to redo command .
> [zk: localhost:2181(CONNECTED) 0] redo -1
> Exception in thread "main" java.lang.NullPointerException
> at java.util.StringTokenizer.(Unknown Source)
> at java.util.StringTokenizer.(Unknown Source)
> at 
> org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227)
> at 
> org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645)
> at 
> org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588)
> at 
> org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2467 PreCommit Build #3491

2016-10-16 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2467
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3491/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 139 lines...]
 [exec] PATCH APPLICATION FAILED
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] -1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12833640/ZOOKEEPER-2467.patch
 [exec]   against trunk revision 422058c222a8a31ec7cfd4113fbdc036181f751d.
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 4 new or 
modified tests.
 [exec] 
 [exec] -1 patch.  The patch command could not apply the patch.
 [exec] 
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3491//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] 5d6bec37a51f2ab7b9001ac98b2772b2e74d0cf2 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess’ 
and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess’ 
are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/build.xml:1605: 
exec returned: 1

Total time: 52 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2467
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



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

[jira] [Updated] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2467:

Fix Version/s: (was: 3.5.1)
   3.6.0

> NullPointerException when redo Command is passed negative value
> ---
>
> Key: ZOOKEEPER-2467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.8, 3.5.1, 3.5.2
> Environment: Linux , windows
>Reporter: Joshi Shankar
>Assignee: Rakesh Kumar Singh
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch
>
>
> When negative value of argument is passed to redo command .
> [zk: localhost:2181(CONNECTED) 0] redo -1
> Exception in thread "main" java.lang.NullPointerException
> at java.util.StringTokenizer.(Unknown Source)
> at java.util.StringTokenizer.(Unknown Source)
> at 
> org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227)
> at 
> org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645)
> at 
> org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588)
> at 
> org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2467:

Attachment: ZOOKEEPER-2467-br3-4.patch

Attached committed patches to the jira. Following are the modifictions.

* Test case is renamed to {{testRedoWithNegativeCmdNumber}}
* Used {{System.setOut()}} in branch3-4 patch

> NullPointerException when redo Command is passed negative value
> ---
>
> Key: ZOOKEEPER-2467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.8, 3.5.1, 3.5.2
> Environment: Linux , windows
>Reporter: Joshi Shankar
>Assignee: Rakesh Kumar Singh
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-br3-4.patch, 
> ZOOKEEPER-2467-final.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch
>
>
> When negative value of argument is passed to redo command .
> [zk: localhost:2181(CONNECTED) 0] redo -1
> Exception in thread "main" java.lang.NullPointerException
> at java.util.StringTokenizer.(Unknown Source)
> at java.util.StringTokenizer.(Unknown Source)
> at 
> org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227)
> at 
> org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645)
> at 
> org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588)
> at 
> org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 466076 lines...]
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-10-16 13:22:28,180 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2016-10-16 13:22:28,308 [myid:127.0.0.1:24687] - INFO  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24687. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 13:22:28,309 [myid:127.0.0.1:24687] - WARN  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1235] - Session 
0x10018a60873 for server 127.0.0.1/127.0.0.1:24687, 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] 2016-10-16 13:22:28,364 [myid:127.0.0.1:24811] - INFO  
[main-SendThread(127.0.0.1:24811):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24811. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 13:22:28,364 [myid:127.0.0.1:24811] - WARN  
[main-SendThread(127.0.0.1:24811):ClientCnxn$SendThread@1235] - Session 
0x20018a987d5 for server 127.0.0.1/127.0.0.1:24811, 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] 2016-10-16 13:22:28,954 [myid:] - INFO  [ProcessThread(sid:0 
cport:24931)::PrepRequestProcessor@605] - Processed session termination for 
sessionid: 0x10018ac77f4
[junit] 2016-10-16 13:22:28,956 [myid:] - INFO  [New I/O worker 
#1811:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port24931,name1=Connections,name2=127.0.0.1,name3=0x10018ac77f4]
[junit] 2016-10-16 13:22:28,956 [myid:] - INFO  [main:ZooKeeper@1315] - 
Session: 0x10018ac77f4 closed
[junit] 2016-10-16 13:22:28,956 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10018ac77f4
[junit] 2016-10-16 13:22:28,956 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 54909
[junit] 2016-10-16 13:22:28,957 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 468
[junit] 2016-10-16 13:22:28,957 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2016-10-16 13:22:28,957 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-16 13:22:28,957 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-16 13:22:28,957 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:24931
[junit] 2016-10-16 13:22:28,959 [myid:] - INFO  [main:ZooKeeperServer@529] 
- shutting down
[junit] 2016-10-16 13:22:28,959 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 13:22:28,959 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-10-16 13:22:28,959 [myid:] - INFO  
[main:PrepRequestProcessor@996] - Shutting down
[junit] 2016-10-16 13:22:28,959 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-10-16 13:22:28,960 [myid:] - INFO  [ProcessThread(sid:0 
cport:24931)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop!
[junit] 2016-10-16 13:22:28,960 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2016-10-16 13:22:28,960 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2016-10-16 13:22:28,960 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port24931,name1=InMemoryDataTree]
[junit] 2016-10-16 13:22:28,960 [myid:] - INFO  [mai

[jira] [Updated] (ZOOKEEPER-2611) zoo_remove_watchers - can remove the wrong watch

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2611:

Fix Version/s: 3.6.0
   3.5.3

> zoo_remove_watchers - can remove the wrong watch 
> -
>
> Key: ZOOKEEPER-2611
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2611
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Reporter: Eyal leshem
>Priority: Critical
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2611.patch
>
>
> The actual problem is in the function "removeWatcherFromList" - 
> That when we check if we need to delete the watch -  we compare the 
> WatcherCtx to one node before the one we want to delete.. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2611) zoo_remove_watchers - can remove the wrong watch

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R commented on ZOOKEEPER-2611:
-

[~rgs], I've added the fix version to the jira, please feel free to edit if 
needed.

[~fpj], could you please add [~Eyal.leshem] to the contributor list and assign 
the work to him. Thanks!

> zoo_remove_watchers - can remove the wrong watch 
> -
>
> Key: ZOOKEEPER-2611
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2611
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Reporter: Eyal leshem
>Priority: Critical
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2611.patch
>
>
> The actual problem is in the function "removeWatcherFromList" - 
> That when we check if we need to delete the watch -  we compare the 
> WatcherCtx to one node before the one we want to delete.. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2611) zoo_remove_watchers - can remove the wrong watch

2016-10-16 Thread Flavio Junqueira (JIRA)


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

Flavio Junqueira updated ZOOKEEPER-2611:

Assignee: Eyal leshem

> zoo_remove_watchers - can remove the wrong watch 
> -
>
> Key: ZOOKEEPER-2611
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2611
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Reporter: Eyal leshem
>Assignee: Eyal leshem
>Priority: Critical
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2611.patch
>
>
> The actual problem is in the function "removeWatcherFromList" - 
> That when we check if we need to delete the watch -  we compare the 
> WatcherCtx to one node before the one we want to delete.. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value

2016-10-16 Thread Hudson (JIRA)


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

Hudson commented on ZOOKEEPER-2467:
---

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #3121 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/3121/])
ZOOKEEPER-2467: NullPointerException when redo Command is passed (rakeshr: rev 
422058c222a8a31ec7cfd4113fbdc036181f751d)
* (edit) CHANGES.txt
* (edit) src/java/main/org/apache/zookeeper/ZooKeeperMain.java
* (edit) src/java/test/org/apache/zookeeper/ZooKeeperTest.java


> NullPointerException when redo Command is passed negative value
> ---
>
> Key: ZOOKEEPER-2467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.8, 3.5.1, 3.5.2
> Environment: Linux , windows
>Reporter: Joshi Shankar
>Assignee: Rakesh Kumar Singh
>Priority: Minor
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-br3-4.patch, 
> ZOOKEEPER-2467-final.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, 
> ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch
>
>
> When negative value of argument is passed to redo command .
> [zk: localhost:2181(CONNECTED) 0] redo -1
> Exception in thread "main" java.lang.NullPointerException
> at java.util.StringTokenizer.(Unknown Source)
> at java.util.StringTokenizer.(Unknown Source)
> at 
> org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227)
> at 
> org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645)
> at 
> org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588)
> at 
> org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper-trunk-solaris - Build # 1350 - Still Failing

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 439182 lines...]
[junit] 2016-10-16 14:20:41,128 [myid:] - INFO  [main:ClientBase@386] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-10-16 14:20:41,128 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-10-16 14:20:41,129 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-10-16 14:20:41,129 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-10-16 14:20:41,130 [myid:] - INFO  [main:ZooKeeperServer@889] 
- minSessionTimeout set to 6000
[junit] 2016-10-16 14:20:41,130 [myid:] - INFO  [main:ZooKeeperServer@898] 
- maxSessionTimeout set to 6
[junit] 2016-10-16 14:20:41,130 [myid:] - INFO  [main:ZooKeeperServer@159] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test2848582692374360001.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test2848582692374360001.junit.dir/version-2
[junit] 2016-10-16 14:20:41,131 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test2848582692374360001.junit.dir/version-2/snapshot.b
[junit] 2016-10-16 14:20:41,133 [myid:] - INFO  [main:FileTxnSnapLog@306] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test2848582692374360001.junit.dir/version-2/snapshot.b
[junit] 2016-10-16 14:20:41,135 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 14:20:41,135 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-10-16 14:20:41,135 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:33154
[junit] 2016-10-16 14:20:41,136 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:33154
[junit] 2016-10-16 14:20:41,136 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-10-16 14:20:41,136 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:33154 (no session established for client)
[junit] 2016-10-16 14:20:41,136 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-16 14:20:41,138 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-10-16 14:20:41,138 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-10-16 14:20:41,138 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-10-16 14:20:41,138 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-10-16 14:20:41,138 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17867
[junit] 2016-10-16 14:20:41,139 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-10-16 14:20:41,139 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-10-16 14:20:41,139 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-16 14:20:41,212 [myid:] - INFO  [main:ZooKeeper@1315] - 
Session: 0x1244ad88d37 closed
[junit] 2016-10-16 14:20:41,212 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-16 14:20:41,212 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1244ad88d37
[junit] 2016-10-16 14:20:41,212 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-10-16 14:20:41,212 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-10-16 14:20:41,212 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583

ZooKeeper_branch34_jdk7 - Build # 1262 - Failure

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 226542 lines...]
[junit] 2016-10-16 14:37:30,064 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-10-16 14:37:30,064 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-10-16 14:37:30,065 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 14:37:30,065 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-10-16 14:37:30,065 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-10-16 14:37:30,065 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-10-16 14:37:30,065 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-10-16 14:37:30,066 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-10-16 14:37:30,066 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-10-16 14:37:30,067 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-16 14:37:30,068 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-10-16 14:37:30,069 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-10-16 14:37:30,069 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-10-16 14:37:30,070 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-10-16 14:37:30,070 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-10-16 14:37:30,070 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test2139785186710812290.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test2139785186710812290.junit.dir/version-2
[junit] 2016-10-16 14:37:30,075 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 14:37:30,075 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-16 14:37:30,076 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:55415
[junit] 2016-10-16 14:37:30,076 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:55415
[junit] 2016-10-16 14:37:30,077 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-10-16 14:37:30,077 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:55415 (no session established for client)
[junit] 2016-10-16 14:37:30,078 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-16 14:37:30,080 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-10-16 14:37:30,080 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-10-16 14:37:30,080 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-10-16 14:37:30,080 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-10-16 14:37:30,081 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32605
[junit] 2016-10-16 14:37:30,081 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-10-16 14:37:30,081 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-10-16 14:37:30,081 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-10-16 14:37:30,146 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x157cded1742 closed
[junit] 2016-10-16 14:37:30,146 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-10-16 14:37:30,146 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x157cded1742
[junit] 2016-10-16 14:37:30,147

[jira] [Commented] (ZOOKEEPER-2615) Zookeeper server holds onto dead/expired session ids in the watch data structures

2016-10-16 Thread Flavio Junqueira (JIRA)


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

Flavio Junqueira commented on ZOOKEEPER-2615:
-

Thanks for having a look, [~fournc]. I think you're right about the race 
between closing the connection and setting new watches. When we expire the 
session, that race goes away because the {{closeSession} and {{setWatches}} are 
serialized in the request processor pipeline, but not for closing connections.

There is one related point I'm unsure about. When I was looking at the code, I 
noticed that only NIO close invokes {{ZooKeeperServer.removeCnxn}} -> 
{{ZKDatabase.removeCnxn}} -> {{DataTree.removeCnxn}}, which remove the watches. 
I'm wondering what that's the case.

> Zookeeper server holds onto dead/expired session ids in the watch data 
> structures
> -
>
> Key: ZOOKEEPER-2615
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2615
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: guoping.gp
>
> The same issue (https://issues.apache.org/jira/browse/ZOOKEEPER-1382) still 
> can be found even with zookeeper 3.4.6.
> this issue cause our production zookeeper cluster leak about 1 million 
> watchs, after restart the server one by one, the watch count decrease to only 
> about 4.
> I can reproduce the issue on my mac,here it is:
> 
> pguodeMacBook-Air:bin pguo$ echo srvr | nc localhost 6181
> Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT
> Latency min/avg/max: 0/1156/128513
> Received: 539
> Sent: 531
> Connections: 1
> Outstanding: 0
> Zxid: 0x10037
> Mode: follower
> Node count: 5
> 
> pguodeMacBook-Air:bin pguo$ echo cons | nc localhost 6181
>  
> /127.0.0.1:55759[1](queued=0,recved=5,sent=5,sid=0x157be2732de,lop=PING,est=1476372631116,to=15000,lcxid=0x1,lzxid=0x,lresp=1476372646260,llat=8,minlat=0,avglat=6,maxlat=17)
>  /0:0:0:0:0:0:0:1:55767[0](queued=0,recved=1,sent=0)
> 
> pguodeMacBook-Air:bin pguo$ echo wchp | nc localhost 6181
> /curator_exists_watch
>   0x357be48e4d90007
>   0x357be48e4d90009
>   0x157be2732de
> as above 4-letter's report shows, 0x357be48e4d90007 and 0x357be48e4d90009 
> are leaked after the two sessions expired 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2615) Zookeeper server holds onto dead/expired session ids in the watch data structures

2016-10-16 Thread Flavio Junqueira (JIRA)


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

Flavio Junqueira updated ZOOKEEPER-2615:

Assignee: Camille Fournier

> Zookeeper server holds onto dead/expired session ids in the watch data 
> structures
> -
>
> Key: ZOOKEEPER-2615
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2615
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: guoping.gp
>Assignee: Camille Fournier
>
> The same issue (https://issues.apache.org/jira/browse/ZOOKEEPER-1382) still 
> can be found even with zookeeper 3.4.6.
> this issue cause our production zookeeper cluster leak about 1 million 
> watchs, after restart the server one by one, the watch count decrease to only 
> about 4.
> I can reproduce the issue on my mac,here it is:
> 
> pguodeMacBook-Air:bin pguo$ echo srvr | nc localhost 6181
> Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT
> Latency min/avg/max: 0/1156/128513
> Received: 539
> Sent: 531
> Connections: 1
> Outstanding: 0
> Zxid: 0x10037
> Mode: follower
> Node count: 5
> 
> pguodeMacBook-Air:bin pguo$ echo cons | nc localhost 6181
>  
> /127.0.0.1:55759[1](queued=0,recved=5,sent=5,sid=0x157be2732de,lop=PING,est=1476372631116,to=15000,lcxid=0x1,lzxid=0x,lresp=1476372646260,llat=8,minlat=0,avglat=6,maxlat=17)
>  /0:0:0:0:0:0:0:1:55767[0](queued=0,recved=1,sent=0)
> 
> pguodeMacBook-Air:bin pguo$ echo wchp | nc localhost 6181
> /curator_exists_watch
>   0x357be48e4d90007
>   0x357be48e4d90009
>   0x157be2732de
> as above 4-letter's report shows, 0x357be48e4d90007 and 0x357be48e4d90009 
> are leaked after the two sessions expired 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2615) Zookeeper server holds onto dead/expired session ids in the watch data structures

2016-10-16 Thread Flavio Junqueira (JIRA)


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

Flavio Junqueira updated ZOOKEEPER-2615:

Fix Version/s: 3.6.0
   3.5.3
   3.4.10

> Zookeeper server holds onto dead/expired session ids in the watch data 
> structures
> -
>
> Key: ZOOKEEPER-2615
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2615
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: guoping.gp
>Assignee: Camille Fournier
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> The same issue (https://issues.apache.org/jira/browse/ZOOKEEPER-1382) still 
> can be found even with zookeeper 3.4.6.
> this issue cause our production zookeeper cluster leak about 1 million 
> watchs, after restart the server one by one, the watch count decrease to only 
> about 4.
> I can reproduce the issue on my mac,here it is:
> 
> pguodeMacBook-Air:bin pguo$ echo srvr | nc localhost 6181
> Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT
> Latency min/avg/max: 0/1156/128513
> Received: 539
> Sent: 531
> Connections: 1
> Outstanding: 0
> Zxid: 0x10037
> Mode: follower
> Node count: 5
> 
> pguodeMacBook-Air:bin pguo$ echo cons | nc localhost 6181
>  
> /127.0.0.1:55759[1](queued=0,recved=5,sent=5,sid=0x157be2732de,lop=PING,est=1476372631116,to=15000,lcxid=0x1,lzxid=0x,lresp=1476372646260,llat=8,minlat=0,avglat=6,maxlat=17)
>  /0:0:0:0:0:0:0:1:55767[0](queued=0,recved=1,sent=0)
> 
> pguodeMacBook-Air:bin pguo$ echo wchp | nc localhost 6181
> /curator_exists_watch
>   0x357be48e4d90007
>   0x357be48e4d90009
>   0x157be2732de
> as above 4-letter's report shows, 0x357be48e4d90007 and 0x357be48e4d90009 
> are leaked after the two sessions expired 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

3.6.0-alpha release?

2016-10-16 Thread Flavio Junqueira

Hello there,

There are a few things interesting in trunk, like the TTL nodes feature and the 
performance improvement in ZK-2024, and I've been wondering if it would make 
sense to cut an alpha release for folks to start testing. Points to keep in 
mind are:

- Positive: There are features that would be good to make available through a 
release so that the community can start testing more broadly.
- Negative: Our focus will remain in 3.5 until it stabilizes, so creating a 3.6 
branch will create some additional burden to the community.

Any thoughts here? 

-Flavio

[jira] [Updated] (ZOOKEEPER-2576) After svn to git migration ZooKeeper Precommit jenkins job is failing.

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2576:

Fix Version/s: 3.6.0

> After svn to git migration ZooKeeper Precommit jenkins job is failing.
> --
>
> Key: ZOOKEEPER-2576
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2576
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: build
>Reporter: Patrick Hunt
>Assignee: Patrick Hunt
>Priority: Blocker
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2576-part2.patch, ZOOKEEPER-2576.patch
>
>
> After moving from svn to git the precommit job is failing. I've disabled it 
> temporarily.
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2615) Zookeeper server holds onto dead/expired session ids in the watch data structures

2016-10-16 Thread Camille Fournier (JIRA)


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

Camille Fournier commented on ZOOKEEPER-2615:
-

I noticed that as well. Does anyone actually use the Netty implementations in 
production?

> Zookeeper server holds onto dead/expired session ids in the watch data 
> structures
> -
>
> Key: ZOOKEEPER-2615
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2615
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: guoping.gp
>Assignee: Camille Fournier
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> The same issue (https://issues.apache.org/jira/browse/ZOOKEEPER-1382) still 
> can be found even with zookeeper 3.4.6.
> this issue cause our production zookeeper cluster leak about 1 million 
> watchs, after restart the server one by one, the watch count decrease to only 
> about 4.
> I can reproduce the issue on my mac,here it is:
> 
> pguodeMacBook-Air:bin pguo$ echo srvr | nc localhost 6181
> Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT
> Latency min/avg/max: 0/1156/128513
> Received: 539
> Sent: 531
> Connections: 1
> Outstanding: 0
> Zxid: 0x10037
> Mode: follower
> Node count: 5
> 
> pguodeMacBook-Air:bin pguo$ echo cons | nc localhost 6181
>  
> /127.0.0.1:55759[1](queued=0,recved=5,sent=5,sid=0x157be2732de,lop=PING,est=1476372631116,to=15000,lcxid=0x1,lzxid=0x,lresp=1476372646260,llat=8,minlat=0,avglat=6,maxlat=17)
>  /0:0:0:0:0:0:0:1:55767[0](queued=0,recved=1,sent=0)
> 
> pguodeMacBook-Air:bin pguo$ echo wchp | nc localhost 6181
> /curator_exists_watch
>   0x357be48e4d90007
>   0x357be48e4d90009
>   0x157be2732de
> as above 4-letter's report shows, 0x357be48e4d90007 and 0x357be48e4d90009 
> are leaked after the two sessions expired 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: 3.6.0-alpha release?

2016-10-16 Thread Jordan Zimmerman

Obviously, I’d love to see TTL nodes released. For our needs, FWIW, at 
Elasticsearch we also need ZOOKEEPER-1525 
 released.

-Jordan

> On Oct 16, 2016, at 9:55 AM, Flavio Junqueira  wrote:
> 
> Hello there,
> 
> There are a few things interesting in trunk, like the TTL nodes feature and 
> the performance improvement in ZK-2024, and I've been wondering if it would 
> make sense to cut an alpha release for folks to start testing. Points to keep 
> in mind are:
> 
> - Positive: There are features that would be good to make available through a 
> release so that the community can start testing more broadly.
> - Negative: Our focus will remain in 3.5 until it stabilizes, so creating a 
> 3.6 branch will create some additional burden to the community.
> 
> Any thoughts here? 
> 
> -Flavio

[jira] [Commented] (ZOOKEEPER-2442) Socket leak in QuorumCnxManager connectOne

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R commented on ZOOKEEPER-2442:
-

I think this has to be back ported to {{branch-3.5}}, shall I merge this to 
branch-3.5, any comments?

> Socket leak in QuorumCnxManager connectOne
> --
>
> Key: ZOOKEEPER-2442
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2442
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum, server
>Affects Versions: 3.5.1
>Reporter: Michael Han
>Assignee: Michael Han
> Attachments: ZOOKEEPER-2442.patch
>
>
> The function connectOne() in QuorumCnxManager.java sometimes fails to release 
> a socket allocated by Socket():
> {code}
>  try {
> if (LOG.isDebugEnabled()) {
> LOG.debug("Opening channel to server " + sid);
> }
> Socket sock = new Socket();
> setSockOpts(sock);
> sock.connect(self.getView().get(sid).electionAddr, cnxTO);
> if (LOG.isDebugEnabled()) {
> LOG.debug("Connected to server " + sid);
> }
> initiateConnection(sock, sid);
> } catch (UnresolvedAddressException e) {
> // Sun doesn't include the address that causes this
> // exception to be thrown, also UAE cannot be wrapped cleanly
> // so we log the exception in order to capture this critical
> // detail.
> LOG.warn("Cannot open channel to " + sid
> + " at election address " + electionAddr, e);
> throw e;
> } catch (IOException e) {
> LOG.warn("Cannot open channel to " + sid
> + " at election address " + electionAddr,
> e);
> }
> {code}
> Another place in Listener.run() where the client socket is not explicitly 
> closed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2615) Zookeeper server holds onto dead/expired session ids in the watch data structures

2016-10-16 Thread Edward Ribeiro (JIRA)


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

Edward Ribeiro commented on ZOOKEEPER-2615:
---

https://issues.apache.org/jira/plugins/servlet/mobile#issue/ZOOKEEPER-2358

The issue above addresses Netty issue.

> Zookeeper server holds onto dead/expired session ids in the watch data 
> structures
> -
>
> Key: ZOOKEEPER-2615
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2615
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: guoping.gp
>Assignee: Camille Fournier
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> The same issue (https://issues.apache.org/jira/browse/ZOOKEEPER-1382) still 
> can be found even with zookeeper 3.4.6.
> this issue cause our production zookeeper cluster leak about 1 million 
> watchs, after restart the server one by one, the watch count decrease to only 
> about 4.
> I can reproduce the issue on my mac,here it is:
> 
> pguodeMacBook-Air:bin pguo$ echo srvr | nc localhost 6181
> Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT
> Latency min/avg/max: 0/1156/128513
> Received: 539
> Sent: 531
> Connections: 1
> Outstanding: 0
> Zxid: 0x10037
> Mode: follower
> Node count: 5
> 
> pguodeMacBook-Air:bin pguo$ echo cons | nc localhost 6181
>  
> /127.0.0.1:55759[1](queued=0,recved=5,sent=5,sid=0x157be2732de,lop=PING,est=1476372631116,to=15000,lcxid=0x1,lzxid=0x,lresp=1476372646260,llat=8,minlat=0,avglat=6,maxlat=17)
>  /0:0:0:0:0:0:0:1:55767[0](queued=0,recved=1,sent=0)
> 
> pguodeMacBook-Air:bin pguo$ echo wchp | nc localhost 6181
> /curator_exists_watch
>   0x357be48e4d90007
>   0x357be48e4d90009
>   0x157be2732de
> as above 4-letter's report shows, 0x357be48e4d90007 and 0x357be48e4d90009 
> are leaked after the two sessions expired 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2442) Socket leak in QuorumCnxManager connectOne

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2442:

Fix Version/s: 3.6.0

> Socket leak in QuorumCnxManager connectOne
> --
>
> Key: ZOOKEEPER-2442
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2442
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum, server
>Affects Versions: 3.5.1
>Reporter: Michael Han
>Assignee: Michael Han
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2442.patch
>
>
> The function connectOne() in QuorumCnxManager.java sometimes fails to release 
> a socket allocated by Socket():
> {code}
>  try {
> if (LOG.isDebugEnabled()) {
> LOG.debug("Opening channel to server " + sid);
> }
> Socket sock = new Socket();
> setSockOpts(sock);
> sock.connect(self.getView().get(sid).electionAddr, cnxTO);
> if (LOG.isDebugEnabled()) {
> LOG.debug("Connected to server " + sid);
> }
> initiateConnection(sock, sid);
> } catch (UnresolvedAddressException e) {
> // Sun doesn't include the address that causes this
> // exception to be thrown, also UAE cannot be wrapped cleanly
> // so we log the exception in order to capture this critical
> // detail.
> LOG.warn("Cannot open channel to " + sid
> + " at election address " + electionAddr, e);
> throw e;
> } catch (IOException e) {
> LOG.warn("Cannot open channel to " + sid
> + " at election address " + electionAddr,
> e);
> }
> {code}
> Another place in Listener.run() where the client socket is not explicitly 
> closed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2335) Java Compilation Error in ClientCnxn.java

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2335:

Fix Version/s: 3.5.2
   3.6.0

> Java Compilation Error in ClientCnxn.java
> -
>
> Key: ZOOKEEPER-2335
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2335
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client, server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2335-01.patch, ZOOKEEPER-2335-01.patch
>
>
> There  are some compilation error in latest trunk code.
> {code}
> [javac] 
> D:\gitHome\zookeeperTrunk\src\java\main\org\apache\zookeeper\ClientCnxn.java:49:
>  error: package org.apache.log4j does not exist
> [javac] import org.apache.log4j.MDC;
> [javac]^
> [javac] 
> D:\gitHome\zookeeperTrunk\src\java\main\org\apache\zookeeper\ClientCnxn.java:1108:
>  error: cannot find symbol
> [javac] MDC.put("myid", hostPort);
> [javac] ^
> [javac]   symbol:   variable MDC
> [javac]   location: class ClientCnxn.SendThread
> [javac] 2 errors
> {code}
> This compilation error got introduced by ZOOKEEPER-2330 patch. This patch 
> used log4j api and log4 dependency has already been removed by ZOOKEEPER-1371



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2270) Allow MBeanRegistry to be overridden for better unit tests

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2270:

Fix Version/s: 3.4.7
   3.5.2
   3.6.0

> Allow MBeanRegistry to be overridden for better unit tests
> --
>
> Key: ZOOKEEPER-2270
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2270
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2270.2.patch, ZOOKEEPER-2270.patch
>
>
> Apache Curator currently must use byte code re-writing to prevent the 
> MBeanRegistry from polluting the Platform MBeanServer. Provide a simple way 
> to avoid this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2271) Allow MBeanRegistry to be overridden for better unit tests in 3.4.x

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2271:

Fix Version/s: 3.4.7

> Allow MBeanRegistry to be overridden for better unit tests in 3.4.x
> ---
>
> Key: ZOOKEEPER-2271
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2271
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: server
>Affects Versions: 3.4.6
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Fix For: 3.4.7
>
> Attachments: ZOOKEEPER-2271.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2270) Allow MBeanRegistry to be overridden for better unit tests

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R updated ZOOKEEPER-2270:

Fix Version/s: (was: 3.4.7)

> Allow MBeanRegistry to be overridden for better unit tests
> --
>
> Key: ZOOKEEPER-2270
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2270
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2270.2.patch, ZOOKEEPER-2270.patch
>
>
> Apache Curator currently must use byte code re-writing to prevent the 
> MBeanRegistry from polluting the Platform MBeanServer. Provide a simple way 
> to avoid this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2355) Ephemeral node is never deleted if follower fails while reading the proposal packet

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R commented on ZOOKEEPER-2355:
-

+1, latest patch looks good to me.

ping  [~fpj], [~rgs], I will wait to see your votes before commits. Thanks!

> Ephemeral node is never deleted if follower fails while reading the proposal 
> packet
> ---
>
> Key: ZOOKEEPER-2355
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2355
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum, server
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Critical
> Fix For: 3.4.10, 3.5.3
>
> Attachments: ZOOKEEPER-2355-01.patch, ZOOKEEPER-2355-02.patch, 
> ZOOKEEPER-2355-03.patch, ZOOKEEPER-2355-04.patch, ZOOKEEPER-2355-05.patch
>
>
> ZooKeeper ephemeral node is never deleted if follower fail while reading the 
> proposal packet
> The scenario is as follows:
> # Configure three node ZooKeeper cluster, lets say nodes are A, B and C, 
> start all, assume A is leader, B and C are follower
> # Connect to any of the server and create ephemeral node /e1
> # Close the session, ephemeral node /e1 will go for deletion
> # While receiving delete proposal make Follower B to fail with 
> {{SocketTimeoutException}}. This we need to do to reproduce the scenario 
> otherwise in production environment it happens because of network fault.
> # Remove the fault, just check that faulted Follower is now connected with 
> quorum
> # Connect to any of the server, create the same ephemeral node /e1, created 
> is success.
> # Close the session,  ephemeral node /e1 will go for deletion
> # {color:red}/e1 is not deleted from the faulted Follower B, It should have 
> been deleted as it was again created with another session{color}
> # {color:green}/e1 is deleted from Leader A and other Follower C{color}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2479) Add 'fleTimeTaken' value in LeaderMXBean and FollowerMXBean

2016-10-16 Thread Rakesh R (JIRA)


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

Rakesh R commented on ZOOKEEPER-2479:
-

[~fpj] could you please help me to push this in. Thanks!

> Add 'fleTimeTaken' value in LeaderMXBean and FollowerMXBean
> ---
>
> Key: ZOOKEEPER-2479
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2479
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: quorum
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2479.patch, ZOOKEEPER-2479.patch, 
> ZOOKEEPER-2479.patch, ZOOKEEPER-2479.patch
>
>
> The idea of this jira is to expose {{time taken}} for the leader election via 
> jmx Leader, Follower beans.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2479) Add 'fleTimeTaken' value in LeaderMXBean and FollowerMXBean

2016-10-16 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on ZOOKEEPER-2479:
--

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12821253/ZOOKEEPER-2479.patch
  against trunk revision 422058c222a8a31ec7cfd4113fbdc036181f751d.

+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 2.0.3) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

+1 core tests.  The patch passed core unit tests.

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3492//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3492//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3492//console

This message is automatically generated.

> Add 'fleTimeTaken' value in LeaderMXBean and FollowerMXBean
> ---
>
> Key: ZOOKEEPER-2479
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2479
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: quorum
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2479.patch, ZOOKEEPER-2479.patch, 
> ZOOKEEPER-2479.patch, ZOOKEEPER-2479.patch
>
>
> The idea of this jira is to expose {{time taken}} for the leader election via 
> jmx Leader, Follower beans.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Success: ZOOKEEPER-2479 PreCommit Build #3492

2016-10-16 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2479
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3492/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 441689 lines...]
 [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 2.0.3) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3492//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3492//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3492//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] 82a0ff579f9b5d46f616e331b9692979f1bc89de logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess’ 
and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess’ 
are the same file

BUILD SUCCESSFUL
Total time: 17 minutes 42 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-2479
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
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



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

ZooKeeper_branch34_openjdk7 - Build # 1245 - Still Failing

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 223710 lines...]
[junit] 2016-10-16 16:29:13,992 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-10-16 16:29:13,992 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-10-16 16:29:13,993 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 16:29:13,993 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-10-16 16:29:13,993 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-10-16 16:29:13,993 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-10-16 16:29:13,993 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-10-16 16:29:13,994 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-10-16 16:29:13,994 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-10-16 16:29:13,995 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-16 16:29:13,995 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-10-16 16:29:13,997 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-10-16 16:29:13,997 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-10-16 16:29:13,998 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-10-16 16:29:13,998 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-10-16 16:29:13,999 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/build/test/tmp/test4209270726567191364.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/build/test/tmp/test4209270726567191364.junit.dir/version-2
[junit] 2016-10-16 16:29:14,003 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 16:29:14,004 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-16 16:29:14,004 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:42362
[junit] 2016-10-16 16:29:14,005 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:42362
[junit] 2016-10-16 16:29:14,005 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-10-16 16:29:14,006 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:42362 (no session established for client)
[junit] 2016-10-16 16:29:14,006 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-16 16:29:14,008 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-10-16 16:29:14,009 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-10-16 16:29:14,009 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-10-16 16:29:14,009 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-10-16 16:29:14,009 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32635
[junit] 2016-10-16 16:29:14,010 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-10-16 16:29:14,010 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-10-16 16:29:14,010 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-10-16 16:29:14,055 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x157ce536167 closed
[junit] 2016-10-16 16:29:14,056 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-10-16 16:29:14,056 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x157ce536167
[junit] 2016-10-16

ZooKeeper_branch35_solaris - Build # 285 - Still Failing

2016-10-16 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/285/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 439944 lines...]
[junit] 2016-10-16 18:11:39,624 [myid:] - INFO  [main:ClientBase@386] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-10-16 18:11:39,625 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-10-16 18:11:39,625 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-10-16 18:11:39,626 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-10-16 18:11:39,626 [myid:] - INFO  [main:ZooKeeperServer@889] 
- minSessionTimeout set to 6000
[junit] 2016-10-16 18:11:39,626 [myid:] - INFO  [main:ZooKeeperServer@898] 
- maxSessionTimeout set to 6
[junit] 2016-10-16 18:11:39,627 [myid:] - INFO  [main:ZooKeeperServer@159] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test6022840648226227902.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test6022840648226227902.junit.dir/version-2
[junit] 2016-10-16 18:11:39,627 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test6022840648226227902.junit.dir/version-2/snapshot.b
[junit] 2016-10-16 18:11:39,629 [myid:] - INFO  [main:FileTxnSnapLog@306] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test6022840648226227902.junit.dir/version-2/snapshot.b
[junit] 2016-10-16 18:11:39,630 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 18:11:39,631 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-10-16 18:11:39,631 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:58369
[junit] 2016-10-16 18:11:39,632 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:58369
[junit] 2016-10-16 18:11:39,632 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-10-16 18:11:39,632 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:58369 (no session established for client)
[junit] 2016-10-16 18:11:39,632 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-16 18:11:39,634 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-10-16 18:11:39,634 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-10-16 18:11:39,634 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-10-16 18:11:39,634 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-10-16 18:11:39,634 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17684
[junit] 2016-10-16 18:11:39,635 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-10-16 18:11:39,635 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-10-16 18:11:39,635 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-16 18:11:39,712 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1244bac043d closed
[junit] 2016-10-16 18:11:39,712 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1244bac043d
[junit] 2016-10-16 18:11:39,712 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-16 18:11:39,712 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-10-16 18:11:39,712 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-10-16 18:11:39,712 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@4

ZooKeeper-trunk-openjdk7 - Build # 1205 - Failure

2016-10-16 Thread Apache Jenkins Server

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 452399 lines...]
[junit] 2016-10-16 20:02:43,432 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1001e3883e9
[junit] 2016-10-16 20:02:43,433 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 128352
[junit] 2016-10-16 20:02:43,433 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 467
[junit] 2016-10-16 20:02:43,434 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2016-10-16 20:02:43,436 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-16 20:02:43,436 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-16 20:02:43,436 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:22238
[junit] 2016-10-16 20:02:43,435 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22238,name1=Connections,name2=127.0.0.1,name3=0x1001e3883e9]
[junit] 2016-10-16 20:02:43,444 [myid:] - INFO  [main:ZooKeeperServer@529] 
- shutting down
[junit] 2016-10-16 20:02:43,445 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-16 20:02:43,445 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2016-10-16 20:02:43,445 [myid:] - INFO  
[main:PrepRequestProcessor@996] - Shutting down
[junit] 2016-10-16 20:02:43,445 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2016-10-16 20:02:43,446 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2016-10-16 20:02:43,446 [myid:] - INFO  [ProcessThread(sid:0 
cport:22238)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop!
[junit] 2016-10-16 20:02:43,446 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2016-10-16 20:02:43,446 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22238,name1=InMemoryDataTree]
[junit] 2016-10-16 20:02:43,447 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port22238]
[junit] 2016-10-16 20:02:43,447 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 22238
[junit] 2016-10-16 20:02:43,448 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-10-16 20:02:43,454 [myid:] - INFO  [main:ClientBase@568] - 
fdcount after test is: 1385 at start it was 1381
[junit] 2016-10-16 20:02:43,454 [myid:] - INFO  [main:ClientBase@570] - 
sleeping for 20 secs
[junit] 2016-10-16 20:02:43,454 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2016-10-16 20:02:43,454 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
431.7 sec, Thread: 5, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2016-10-16 20:02:43,531 [myid:127.0.0.1:22121] - INFO  
[main-SendThread(127.0.0.1:22121):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:22121. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 20:02:43,532 [myid:127.0.0.1:22121] - WARN  
[main-SendThread(127.0.0.1:22121):ClientCnxn$SendThread@1235] - Session 
0x3001e35aaa3 for server 127.0.0.1/127.0.0.1:22121, 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] 2016-10-16 20:02:43,834 [myid:127.0.0.1:21994] - INFO  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:21994. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-16 20:02:43,835 [myid:127.0.0.1:21994] - WARN  
[main-SendThread(127.0.0.1:21994):ClientCnxn$SendThread@1235] - Session 
0x1001e3208ed for server 127.0.0.1/127.0.0.1:21994, unexpected error, 
closing socket connection and attempting reconnect
[junit

[jira] [Updated] (ZOOKEEPER-2606) SaslServerCallbackHandler#handleAuthorizeCallback() should log the exception

2016-10-16 Thread Ted Yu (JIRA)


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

Ted Yu updated ZOOKEEPER-2606:
--
Labels: security  (was: )

> SaslServerCallbackHandler#handleAuthorizeCallback() should log the exception
> 
>
> Key: ZOOKEEPER-2606
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2606
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
>  Labels: security
> Attachments: ZOOKEEPER-2606.v1.patch
>
>
> {code}
> LOG.info("Setting authorizedID: " + userNameBuilder);
> ac.setAuthorizedID(userNameBuilder.toString());
> } catch (IOException e) {
> LOG.error("Failed to set name based on Kerberos authentication 
> rules.");
> }
> {code}
> On one cluster, we saw the following:
> {code}
> 2016-10-04 02:18:16,484 - ERROR 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:SaslServerCallbackHandler@137] - 
> Failed to set name based on Kerberos authentication rules.
> {code}
> It would be helpful if the log contains information about the IOException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] zookeeper pull request #87: correct a few spelling typos

2016-10-16 Thread tmancill

GitHub user tmancill opened a pull request:

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

correct a few spelling typos

Hi - this PR contains corrections for some spelling typos.  Most of them 
appear in comments, but a few appear in documentation and program output.  
Thank you for considering it.


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

$ git pull https://github.com/tmancill/zookeeper tmancill/spelling-typos

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

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


commit dbf2f344975d3efe67b034ccd4055acd92a06da7
Author: tony mancill 
Date:   2016-10-17T04:14:00Z

correct a few spelling typos




---
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-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

2016-10-16 Thread Rakesh Kumar Singh (JIRA)


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

Rakesh Kumar Singh commented on ZOOKEEPER-2556:
---

Pls review and commit if looks fine.

> peerType remains as "observer" in zoo.cfg even though we change the node from 
> observer to participant runtime
> -
>
> Key: ZOOKEEPER-2556
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.1, 3.5.2
>Reporter: Rakesh Kumar Singh
>Assignee: Rakesh Kumar Singh
>Priority: Minor
> Attachments: ZOOKEEPER-2556.patch
>
>
> peerType remains as "observer" in zoo.cfg even though we change the node from 
> observer to participant runtime
> Steps to reproduce:-
> 1. Start zookeeper in cluster with one node as observer by configuring 
> peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181
> 2. Start the cluster
> 3. start a client and change the node from observer to participant, the 
> configuration related to peertype remained same though other things like 
> clientport got from zoo.cfg
> >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181
> We should either remove this parameter or update with correct node type at 
> run time



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: [jira] [Commented] (ZOOKEEPER-2615) Zookeeper server holds onto dead/expired session ids in the watch data structures

2016-10-16 Thread Kanniappan, Mohanarangan (Nokia - IN/Bangalore)

I want to unsubscribe please send me procedure anyone.

Regards
Mohan

-Original Message-
From: Camille Fournier (JIRA) [mailto:j...@apache.org] 
Sent: Friday, October 14, 2016 10:58 PM
To: dev@zookeeper.apache.org
Subject: [jira] [Commented] (ZOOKEEPER-2615) Zookeeper server holds onto 
dead/expired session ids in the watch data structures


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

Camille Fournier commented on ZOOKEEPER-2615:
-

OK yup. This is a different race than what we fixed in ZOOKEEPER-1382. Because 
we don't check to see if the watch we're setting is still on a live connection 
when we set it, we can totally race to set a watch vs deleting watches from a 
connection.

Thinking.

> Zookeeper server holds onto dead/expired session ids in the watch data 
> structures
> --
> ---
>
> Key: ZOOKEEPER-2615
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2615
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: guoping.gp
>
> The same issue (https://issues.apache.org/jira/browse/ZOOKEEPER-1382) still 
> can be found even with zookeeper 3.4.6.
> this issue cause our production zookeeper cluster leak about 1 million 
> watchs, after restart the server one by one, the watch count decrease to only 
> about 4.
> I can reproduce the issue on my mac,here it is:
> --
> -- pguodeMacBook-Air:bin pguo$ echo srvr | nc localhost 6181 Zookeeper 
> version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT Latency 
> min/avg/max: 0/1156/128513
> Received: 539
> Sent: 531
> Connections: 1
> Outstanding: 0
> Zxid: 0x10037
> Mode: follower
> Node count: 5
> 
> pguodeMacBook-Air:bin pguo$ echo cons | nc localhost 6181
>  
> /127.0.0.1:55759[1](queued=0,recved=5,sent=5,sid=0x157be2732de,lop
> =PING,est=1476372631116,to=15000,lcxid=0x1,lzxid=0x,lr
> esp=1476372646260,llat=8,minlat=0,avglat=6,maxlat=17)
>  /0:0:0:0:0:0:0:1:55767[0](queued=0,recved=1,sent=0)
> 
> pguodeMacBook-Air:bin pguo$ echo wchp | nc localhost 6181 
> /curator_exists_watch
>   0x357be48e4d90007
>   0x357be48e4d90009
>   0x157be2732de
> as above 4-letter's report shows, 0x357be48e4d90007 and 0x357be48e4d90009 
> are leaked after the two sessions expired 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: 3.6.0-alpha release?

2016-10-16 Thread Michael Han

I think having more frequent release is beneficial to both the project, and
the users and community, so I am +1 on the idea of cutting out a 3.6 alpha
release for new features. Regarding additional burden, my understanding is
the cost would be similar as releasing a beta version such as 3.5.x but
smaller than releasing a stable version 3.4.x (where stability / quality
matters), so it seems manageable.

On Sun, Oct 16, 2016 at 8:04 AM, Jordan Zimmerman <
jor...@jordanzimmerman.com> wrote:

> Obviously, I’d love to see TTL nodes released. For our needs, FWIW, at
> Elasticsearch we also need ZOOKEEPER-1525  jira/browse/ZOOKEEPER-1525> released.
>
> -Jordan
>
> > On Oct 16, 2016, at 9:55 AM, Flavio Junqueira  wrote:
> >
> > Hello there,
> >
> > There are a few things interesting in trunk, like the TTL nodes feature
> and the performance improvement in ZK-2024, and I've been wondering if it
> would make sense to cut an alpha release for folks to start testing. Points
> to keep in mind are:
> >
> > - Positive: There are features that would be good to make available
> through a release so that the community can start testing more broadly.
> > - Negative: Our focus will remain in 3.5 until it stabilizes, so
> creating a 3.6 branch will create some additional burden to the community.
> >
> > Any thoughts here?
> >
> > -Flavio
>
>


-- 
Cheers
Michael.

Re: 3.6.0-alpha release?

2016-10-16 Thread Rakesh Radhakrishnan

Thanks @Flavio for the initiative. +1 on the idea of "3.6.0-alpha" release
plans.

Just a thought - I'm not sure, whether multiple on going alpha
versions(3.5.x-alpha and 3.6.x-alpha) could create confusion to the users.
I'd prefer to make 3.5.x to a beta or a stable version first, then release
3.6.x-alpha soon. I agree to kick start release planning of "3.6.0-alpha"
and discuss tentative release dates so that it would help the
committers/contributors/users to push their interested work.

Best Regards,
Rakesh

On Mon, Oct 17, 2016 at 11:37 AM, Michael Han  wrote:

> I think having more frequent release is beneficial to both the project, and
> the users and community, so I am +1 on the idea of cutting out a 3.6 alpha
> release for new features. Regarding additional burden, my understanding is
> the cost would be similar as releasing a beta version such as 3.5.x but
> smaller than releasing a stable version 3.4.x (where stability / quality
> matters), so it seems manageable.
>
> On Sun, Oct 16, 2016 at 8:04 AM, Jordan Zimmerman <
> jor...@jordanzimmerman.com> wrote:
>
> > Obviously, I’d love to see TTL nodes released. For our needs, FWIW, at
> > Elasticsearch we also need ZOOKEEPER-1525  > jira/browse/ZOOKEEPER-1525> released.
> >
> > -Jordan
> >
> > > On Oct 16, 2016, at 9:55 AM, Flavio Junqueira  wrote:
> > >
> > > Hello there,
> > >
> > > There are a few things interesting in trunk, like the TTL nodes feature
> > and the performance improvement in ZK-2024, and I've been wondering if it
> > would make sense to cut an alpha release for folks to start testing.
> Points
> > to keep in mind are:
> > >
> > > - Positive: There are features that would be good to make available
> > through a release so that the community can start testing more broadly.
> > > - Negative: Our focus will remain in 3.5 until it stabilizes, so
> > creating a 3.6 branch will create some additional burden to the
> community.
> > >
> > > Any thoughts here?
> > >
> > > -Flavio
> >
> >
>
>
> --
> Cheers
> Michael.
>

43 matches

Mail list logo