ZooKeeper-trunk-solaris - Build # 1359 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1359/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 475197 lines...] [junit] 2016-10-24 08:28:55,648 [myid:] - INFO [main:ClientBase@386] - CREATING server instance 127.0.0.1:11222 [junit] 2016-10-24 08:28:55,648 [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-24 08:28:55,649 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2016-10-24 08:28:55,649 [myid:] - INFO [main:ClientBase@361] - STARTING server instance 127.0.0.1:11222 [junit] 2016-10-24 08:28:55,650 [myid:] - INFO [main:ZooKeeperServer@889] - minSessionTimeout set to 6000 [junit] 2016-10-24 08:28:55,650 [myid:] - INFO [main:ZooKeeperServer@898] - maxSessionTimeout set to 6 [junit] 2016-10-24 08:28:55,650 [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/test2910513274795219836.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test2910513274795219836.junit.dir/version-2 [junit] 2016-10-24 08:28:55,651 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test2910513274795219836.junit.dir/version-2/snapshot.b [junit] 2016-10-24 08:28:55,653 [myid:] - INFO [main:FileTxnSnapLog@306] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test2910513274795219836.junit.dir/version-2/snapshot.b [junit] 2016-10-24 08:28:55,654 [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-24 08:28:55,654 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2016-10-24 08:28:55,655 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:50385 [junit] 2016-10-24 08:28:55,655 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:50385 [junit] 2016-10-24 08:28:55,655 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2016-10-24 08:28:55,656 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:50385 (no session established for client) [junit] 2016-10-24 08:28:55,656 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-10-24 08:28:55,657 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2016-10-24 08:28:55,657 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2016-10-24 08:28:55,658 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2016-10-24 08:28:55,658 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2016-10-24 08:28:55,658 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17665 [junit] 2016-10-24 08:28:55,658 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2016-10-24 08:28:55,658 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2016-10-24 08:28:55,658 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-10-24 08:28:55,758 [myid:] - INFO [main:ZooKeeper@1315] - Session: 0x12472c942bd closed [junit] 2016-10-24 08:28:55,758 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-10-24 08:28:55,758 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x12472c942bd [junit] 2016-10-24 08:28:55,759 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-10-24 08:28:55,759 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-10-24 08:28:55,759 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread
ZooKeeper_branch35_jdk7 - Build # 709 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/709/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 464992 lines...] [junit] java.net.ConnectException: Connection refused: 127.0.0.1/127.0.0.1:27507 [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) [junit] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [junit] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 08:51:57,765 [myid:] - INFO [New I/O boss #9504:ClientCnxnSocketNetty@208] - channel is told closing [junit] 2016-10-24 08:51:57,765 [myid:127.0.0.1:27507] - INFO [main-SendThread(127.0.0.1:27507):ClientCnxn$SendThread@1231] - channel for sessionid 0x300158f834c is lost, closing socket connection and attempting reconnect [junit] 2016-10-24 08:51:57,815 [myid:] - INFO [main:ClientBase@568] - fdcount after test is: 5214 at start it was 5214 [junit] 2016-10-24 08:51:57,815 [myid:] - INFO [main:ZKTestCase$1@65] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2016-10-24 08:51:57,815 [myid:] - INFO [main:ZKTestCase$1@60] - FINISHED testWatcherAutoResetWithLocal [junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 561.92 sec, Thread: 7, Class: org.apache.zookeeper.test.NettyNettySuiteTest [junit] 2016-10-24 08:51:58,068 [myid:127.0.0.1:27380] - INFO [main-SendThread(127.0.0.1:27380):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:27380. Will not attempt to authenticate using SASL (unknown error) [junit] 2016-10-24 08:51:58,069 [myid:] - INFO [New I/O boss #66:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {} [junit] java.net.ConnectException: Connection refused: 127.0.0.1/127.0.0.1:27380 [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) [junit] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [junit] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 08:51:58,069 [myid:] - WARN [New I/O boss #66:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 0x4329ce90] EXCEPTION: java.net.ConnectException: Connection refused: 127.0.0.1/127.0.0.1:27380 [junit] java.net.ConnectException: Connection refused: 127.0.0.1/127.0.0.1:27380 [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBos
ZooKeeper_branch35_openjdk7 - Build # 274 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/274/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 457863 lines...] [junit] at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:270) [junit] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:479) [junit] at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:201) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:151) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:315) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) [junit] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [junit] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [junit] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 10:09:48,817 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11466,name1=Connections,name2=127.0.0.1,name3=0x10015da3f2b] [junit] 2016-10-24 10:09:48,918 [myid:] - INFO [main:ZooKeeper@1313] - Session: 0x10015da3f2b closed [junit] 2016-10-24 10:09:48,918 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x10015da3f2b [junit] 2016-10-24 10:09:48,918 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 154838 [junit] 2016-10-24 10:09:48,918 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1642 [junit] 2016-10-24 10:09:48,918 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2016-10-24 10:09:48,919 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-10-24 10:09:48,919 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-10-24 10:09:48,919 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:11466 [junit] 2016-10-24 10:09:48,924 [myid:] - INFO [main:ZooKeeperServer@529] - shutting down [junit] 2016-10-24 10:09:48,924 [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-24 10:09:48,924 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2016-10-24 10:09:48,924 [myid:] - INFO [main:PrepRequestProcessor@965] - Shutting down [junit] 2016-10-24 10:09:48,925 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2016-10-24 10:09:48,925 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2016-10-24 10:09:48,925 [myid:] - INFO [ProcessThread(sid:0 cport:11466)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop! [junit] 2016-10-24 10:09:48,925 [myid:] - INFO [main:FinalRequestProcessor@479] - shutdown of request processor complete [junit] 2016-10-24 10:09:48,925 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11466,name1=InMemoryDataTree] [junit] 2016-10-24 10:09:48,926 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11466] [junit] 2016-10-24 10:09:48,926 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11466 [junit] 2016-10-24 10:09:48,926 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-10-24 10:09:48,932 [myid:] - INFO [main:ClientBase@568] - fdcount after test is: 4836 at start it was 4836 [junit] 2016-10-24 10:09:48,932 [myid:] - INFO [main:ZKTestCase$1@65] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2016-10-24 10:09:48,932 [myid:] - INFO [main:ZKTestCase$1@60] - FINISHED testWatcherAutoResetWithLocal [junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Tim
[jira] [Commented] (ZOOKEEPER-2617) minor typos in the source
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601563#comment-15601563 ] Edward Ribeiro commented on ZOOKEEPER-2617: --- +1, thanks for the patch! :) > minor typos in the source > - > > Key: ZOOKEEPER-2617 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2617 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.4.9 >Reporter: tony mancill >Priority: Trivial > Labels: newbie, patch > Attachments: JIRA-ZOOKEEPER-2617.patch > > > While working on the Debian packaging of ZooKeeper, some misspellings were > detected in the source that affect the documentation, logging, and program > output. > There is a PR against github containing the patch here: > https://github.com/apache/zookeeper/pull/87 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-jdk8 - Build # 794 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/794/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 456663 lines...] [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) [junit] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [junit] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 12:00:23,726 [myid:] - INFO [New I/O boss #66:ClientCnxnSocketNetty@208] - channel is told closing [junit] 2016-10-24 12:00:23,726 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1231] - channel for sessionid 0x102fbd3b2dc is lost, closing socket connection and attempting reconnect [junit] Running org.apache.zookeeper.server.quorum.Zab1_0Test in thread 3 [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec, Thread: 3, Class: org.apache.zookeeper.server.quorum.Zab1_0Test [junit] Test org.apache.zookeeper.server.quorum.Zab1_0Test FAILED (timeout) [junit] 2016-10-24 12:03:00,228 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 131985 [junit] 2016-10-24 12:03:00,228 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 55 [junit] 2016-10-24 12:03:00,228 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testManyChildWatchersAutoReset [junit] 2016-10-24 12:03:00,229 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-10-24 12:03:00,230 [myid:] - INFO [ProcessThread(sid:0 cport:27383)::PrepRequestProcessor@605] - Processed session termination for sessionid: 0x102fbd1d2c7 [junit] 2016-10-24 12:03:00,270 [myid:] - INFO [NIOWorkerThread-2:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port27383,name1=Connections,name2=127.0.0.1,name3=0x102fbd1d2c7] [junit] 2016-10-24 12:03:00,271 [myid:] - INFO [NIOWorkerThread-2:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:46023 which had sessionid 0x102fbd1d2c7 [junit] 2016-10-24 12:03:00,271 [myid:] - INFO [main:ZooKeeper@1315] - Session: 0x102fbd1d2c7 closed [junit] 2016-10-24 12:03:00,272 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x102fbd1d2c7 [junit] 2016-10-24 12:03:00,372 [myid:] - INFO [ProcessThread(sid:0 cport:27383)::PrepRequestProcessor@605] - Processed session termination for sessionid: 0x102fbd1d2c70001 [junit] 2016-10-24 12:03:00,395 [myid:] - INFO [main:ZooKeeper@1315] - Session: 0x102fbd1d2c70001 closed [junit] 2016-10-24 12:03:00,395 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-10-24 12:03:00,395 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x102fbd1d2c70001 [junit] 2016-10-24 12:03:00,395 [myid:] - INFO [NIOWorkerThread-18:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port27383,name1=Connections,name2=127.0.0.1,name3=0x102fbd1d2c70001] [junit] 2016-10-24 12:03:00,398 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-10-24 12:03:00,396 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:27383:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2016-10-24 12:03:00,396 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2016-10-24 12:03:00,398 [myid:] - INFO [NIOWorkerThread-18:NIOServerCnxn@607] - Closed socket connection for client /127.0.0.1:45998 which had sessionid 0x102fbd1d2c70001 [junit] 2016-10-24 12:03:00,399 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2016-10-24 12:03:00,400 [myid:] - INFO [main:ZooKeeperServer@529] - shutting down [junit] 2016-10-24 12:03:00,400 [myid:] - ERROR [main:ZooKeeperServer@501] - ZKShutdow
ZooKeeper_branch35_jdk8 - Build # 277 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/277/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 477581 lines...] [junit] at org.jboss.netty.channel.Channels.close(Channels.java:812) [junit] at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:206) [junit] at org.apache.zookeeper.server.NettyServerCnxn.close(NettyServerCnxn.java:111) [junit] at org.apache.zookeeper.server.NettyServerCnxn.sendBuffer(NettyServerCnxn.java:215) [junit] at org.apache.zookeeper.server.NettyServerCnxn.sendCloseSession(NettyServerCnxn.java:441) [junit] at org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:459) [junit] at org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:182) [junit] at org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113) [junit] 2016-10-24 12:20:06,547 [myid:] - INFO [main:ZooKeeper@1313] - Session: 0x102fbeebca3 closed [junit] 2016-10-24 12:20:06,547 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 153026 [junit] 2016-10-24 12:20:06,547 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1643 [junit] 2016-10-24 12:20:06,547 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2016-10-24 12:20:06,547 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-10-24 12:20:06,547 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-10-24 12:20:06,548 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:30317 [junit] 2016-10-24 12:20:06,548 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x102fbeebca3 [junit] 2016-10-24 12:20:06,562 [myid:] - INFO [main:ZooKeeperServer@529] - shutting down [junit] 2016-10-24 12:20:06,562 [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-24 12:20:06,562 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2016-10-24 12:20:06,562 [myid:] - INFO [main:PrepRequestProcessor@965] - Shutting down [junit] 2016-10-24 12:20:06,562 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2016-10-24 12:20:06,564 [myid:] - INFO [ProcessThread(sid:0 cport:30317)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop! [junit] 2016-10-24 12:20:06,565 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2016-10-24 12:20:06,565 [myid:] - INFO [main:FinalRequestProcessor@479] - shutdown of request processor complete [junit] 2016-10-24 12:20:06,565 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port30317,name1=InMemoryDataTree] [junit] 2016-10-24 12:20:06,565 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port30317] [junit] 2016-10-24 12:20:06,565 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 30317 [junit] 2016-10-24 12:20:06,566 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-10-24 12:20:06,570 [myid:] - INFO [main:ClientBase@568] - fdcount after test is: 4831 at start it was 4831 [junit] 2016-10-24 12:20:06,571 [myid:] - INFO [main:ZKTestCase$1@65] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2016-10-24 12:20:06,571 [myid:] - INFO [main:ZKTestCase$1@60] - FINISHED testWatcherAutoResetWithLocal [junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 596.206 sec, Thread: 8, Class: org.apache.zookeeper.test.NioNettySuiteTest [junit] 2016-10-24 12:20:06,757 [myid:127.0.0.1:30200] - INFO [main-SendThread(127.0.0.1:30200):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30200. Will not attempt to authenticate using SASL (unknown error) [junit] 2016-10-24 12:20:06,757 [myid:127.0.0.1:30200] - WARN [main-SendThread(127.0.0.1:30200):ClientCnxn$SendThread@1235] - Session 0x302fbeb51fa for server 127.0.0.1/127.0.0.1:30200, 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.zooke
ZooKeeper_branch34_solaris - Build # 1336 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1336/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 108 lines...] clover: jute: [javac] Compiling 39 source files to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/classes [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. compile_jute_uptodate: compile_jute: [mkdir] Created dir: /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/java/generated [mkdir] Created dir: /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/c/generated [java] ../../zookeeper.jute Parsed Successfully [java] ../../zookeeper.jute Parsed Successfully [touch] Creating /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/java/generated/.generated ver-gen: [javac] Compiling 1 source file to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/classes svn-revision: [mkdir] Created dir: /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/.revision [exec] svn: '.' is not a working copy version-info: [java] Unknown REVISION number, using -1 build-generated: [javac] Compiling 56 source files to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/classes compile: [javac] Compiling 159 source files to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/classes [javac] /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/java/main/org/apache/zookeeper/Shell.java:276: warning: [serial] serializable class org.apache.zookeeper.Shell.ExitCodeException has no definition of serialVersionUID [javac] public static class ExitCodeException extends IOException { [javac] ^ [javac] /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java:680: warning: [deprecation] org.apache.zookeeper.server.quorum.LeaderElection in org.apache.zookeeper.server.quorum has been deprecated [javac] le = new LeaderElection(this); [javac] ^ [javac] /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java:683: warning: [deprecation] org.apache.zookeeper.server.quorum.AuthFastLeaderElection in org.apache.zookeeper.server.quorum has been deprecated [javac] le = new AuthFastLeaderElection(this); [javac] ^ [javac] /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java:686: warning: [deprecation] org.apache.zookeeper.server.quorum.AuthFastLeaderElection in org.apache.zookeeper.server.quorum has been deprecated [javac] le = new AuthFastLeaderElection(this, true); [javac] ^ [javac] /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java:707: warning: [deprecation] org.apache.zookeeper.server.quorum.LeaderElection in org.apache.zookeeper.server.quorum has been deprecated [javac] electionAlg = new LeaderElection(this); [javac] ^ # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (malloc) failed to allocate 32756 bytes for ChunkPool::allocate # An error report file with more information is saved as: # /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/hs_err_pid10448.log [thread 2 also had an error] Build step 'Invoke Ant' marked build as failure [locks-and-latches] Releasing all the locks [locks-and-latches] All the locks released Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2618) fix ClassNotFoundException on shutdown of client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602510#comment-15602510 ] Flavio Junqueira commented on ZOOKEEPER-2618: - I'm confused, is this a duplicate of ZOOKEEPER-1394? > fix ClassNotFoundException on shutdown of client > > > Key: ZOOKEEPER-2618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2618 > Project: ZooKeeper > Issue Type: Sub-task > Components: java client >Affects Versions: 3.4.9 >Reporter: wu wen >Priority: Minor > Fix For: 3.4.10 > > Attachments: ZOOKEEPER-2618.patch > > > see ZOOKEEPER-1394,We also have this issue. > 2016-10-21 13:17:21.618 ERROR > localhost-startStop-1-SendThread(172.21.134.7:2005) ClientCnxn:414 - from > localhost-startStop-1-SendThread(172.21.134.7:2005) > java.lang.NoClassDefFoundError: org/apache/zookeeper/server/ZooTrace > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1128) > Caused by: java.lang.ClassNotFoundException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1315) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1178) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1139) > ... 1 more > Caused by: java.lang.IllegalStateException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1325) > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1313) > ... 3 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper_branch35_solaris - Build # 294 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_solaris/294/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 405238 lines...] [junit] 2016-10-24 17:17:12,925 [myid:] - WARN [LearnerHandler-/127.0.0.1:33964:LearnerHandler@619] - *** GOODBYE /127.0.0.1:33964 [junit] 2016-10-24 17:17:12,926 [myid:] - WARN [LearnerHandler-/127.0.0.1:33964: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-24 17:17:12,927 [myid:] - INFO [/127.0.0.1:11248:QuorumCnxManager$Listener@659] - Leaving listener [junit] 2016-10-24 17:17:12,926 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5,name2=Leader] [junit] 2016-10-24 17:17:12,927 [myid:] - WARN [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(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-24 17:17:12,927 [myid:] - INFO [main:QuorumBase@398] - Shutting down leader election QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled) [junit] 2016-10-24 17:17:12,927 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):Leader@623] - Shutting down [junit] 2016-10-24 17:17:12,927 [myid:] - WARN [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):QuorumPeer@1158] - PeerState set to LOOKING [junit] 2016-10-24 17:17:12,927 [myid:] - WARN [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):QuorumPeer@1140] - QuorumPeer main thread exited [junit] 2016-10-24 17:17:12,927 [myid:] - INFO [main:QuorumBase@403] - Waiting for QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled) to exit thread [junit] 2016-10-24 17:17:12,927 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5] [junit] 2016-10-24 17:17:12,927 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5] [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.1] [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.2] [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.3] [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [QuorumPeer[myid=5](plain=/127.0.0.1:11253)(secure=disabled):MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.4] [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11249 [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [main:QuorumBase@376] - 127.0.0.1:11249 is no longer accepting client connections [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11250 [junit] 2016-10-24 17:17:12,928 [myid:] - INFO [main:QuorumBase@376] - 127.0.0.1:11250 is no longer accepting client connections [junit] 2016-10-24 17:17:12,929 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11251 [junit] 2016-10-24 17:17:12,929 [myid:] - INFO [main:QuorumBase@376] - 127.0.0.1:11251 is no longer accepting client connections [junit] 2016-10-24 17:17:12,929 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11252 [junit] 2016-10-24 17:17:12,929 [myid:] - INFO [main:QuorumBase@
[jira] [Commented] (ZOOKEEPER-2618) fix ClassNotFoundException on shutdown of client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602659#comment-15602659 ] Michael Han commented on ZOOKEEPER-2618: technically yes, though ZOOKEEPER-2618 is created as a subtask of ZOOKEEPER-1394. > fix ClassNotFoundException on shutdown of client > > > Key: ZOOKEEPER-2618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2618 > Project: ZooKeeper > Issue Type: Sub-task > Components: java client >Affects Versions: 3.4.9 >Reporter: wu wen >Priority: Minor > Fix For: 3.4.10 > > Attachments: ZOOKEEPER-2618.patch > > > see ZOOKEEPER-1394,We also have this issue. > 2016-10-21 13:17:21.618 ERROR > localhost-startStop-1-SendThread(172.21.134.7:2005) ClientCnxn:414 - from > localhost-startStop-1-SendThread(172.21.134.7:2005) > java.lang.NoClassDefFoundError: org/apache/zookeeper/server/ZooTrace > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1128) > Caused by: java.lang.ClassNotFoundException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1315) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1178) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1139) > ... 1 more > Caused by: java.lang.IllegalStateException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1325) > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1313) > ... 3 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2618) fix ClassNotFoundException on shutdown of client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602679#comment-15602679 ] Flavio Junqueira commented on ZOOKEEPER-2618: - Ok, I'm even more confused now. I think [~wuwen] did it by mistake, but I'd like a confirmation. If so, let's just work on it in ZOOKEEPER-1394. > fix ClassNotFoundException on shutdown of client > > > Key: ZOOKEEPER-2618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2618 > Project: ZooKeeper > Issue Type: Sub-task > Components: java client >Affects Versions: 3.4.9 >Reporter: wu wen >Priority: Minor > Fix For: 3.4.10 > > Attachments: ZOOKEEPER-2618.patch > > > see ZOOKEEPER-1394,We also have this issue. > 2016-10-21 13:17:21.618 ERROR > localhost-startStop-1-SendThread(172.21.134.7:2005) ClientCnxn:414 - from > localhost-startStop-1-SendThread(172.21.134.7:2005) > java.lang.NoClassDefFoundError: org/apache/zookeeper/server/ZooTrace > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1128) > Caused by: java.lang.ClassNotFoundException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1315) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1178) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1139) > ... 1 more > Caused by: java.lang.IllegalStateException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1325) > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1313) > ... 3 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2619) Client library reconnecting breaks FIFO client order
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602873#comment-15602873 ] Diego Ongaro commented on ZOOKEEPER-2619: - Thanks for the quick replies. bq. In your first example, you're mixing the synchronous and the asynchronous API. We don't actually enforce that an application uses one or the other, but we do not recommend to mix synchronous and asynchronous calls precisely because of the reasons you're raising. In my three-line example, it doesn't matter whether the second create is synchronous (mixing) or asynchronous (not mixing). Isn't it fine to issue a series of asynchronous calls ending with a synchronous call? Summarizing the *{{reenableOps()}}* proposal so far, we have: - A new configuration option (say, "requireReenableOps") for an application to opt into calling {{reenableOps()}}. This would preserve backwards compatibility for existing clients, so the default would be to keep today's behavior. - Upon a connection loss, the client library would still reconnect automatically and issue pings as needed. However, with the configuration option set, it would continue to fail all requests (both synchronous and asynchronous). - After the application calls {{reenableOps()}}, the client library would permit new requests to use the new connection. This would work, but in terms of API design, I can think of a couple of drawbacks: - If we consider an application that's spread across various modules and/or thread boundaries, it has to be carefully designed with respect to {{reenableOps()}}, as this is a global property. I think this is what [~breed] was getting at with "it affects everything using the zookeeper handle". Specifically, every module/thread must be ready for a call to {{reenableOps()}} before it is safe to invoke, and until such time, the application won't make much progress. - Most asynchronous code will need to know whether it's running under requireReenableOps=false or requireReenableOps=true. This might complicate a reusable library's internals and API, which may need to have different behavior depending on this setting. The *{{getConnection()}}* proposal doesn't have these problems. Some modules of an application can continue issuing synchronous calls on the ZooKeeper object, others can issue (deprecated) asynchronous calls on the ZooKeeper object, and yet others can use ZKConnection objects, moving to new connections at their own pace with no application-level synchronization. bq. it sounds to me that getConnection() and reenableOps() are basically the same. right? or are you proposing that when you get a ZKConnection object you can invoke the zookeeper operations on that? You would invoke the operations directly on the ZKConnection object. I do like the idea of the library automatically reconnecting for pings, and we could apply that to the {{getConnection()}} proposal too: - The library would reconnect automatically to issue pings, as it does now. - {{ZooKeeper.getConnection()}} would return the current ZKConnection object, which wraps the current TCP connection. - Upon a connection loss, all subsequent operations on the same ZKConnection would return a Connection Loss error. The library would internally reconnect automatically, but it would not make this TCP connection availble via the old ZKConnection. - Upon noticing a connection loss, the application would need to call {{ZooKeeper.getConnection()}} again to get the new ZKConnection object. The ZKConnection object certainly needs to export the asynchronous methods that are in ZooKeeper today. I think it should also export the synchronous methods. I think these are both well-defined and useful in ZKConnection, as in my original example with {{createAsync()}} followed by {{createSync()}}. I think the ZooKeeper class should continue to export non-deprecated synchronous methods as well. These would just be convenience wrappers that invoke {{getConnection()}} followed by the synchronous operation on that. Much ZooKeeper code is entirely synchronous, and as such, does not depend on FIFO client order. I see no reason to force churn upon that code. I still think the asynchronous calls on the ZooKeeper class should be deprecated, since applications cannot rely on FIFO client order when using them. At a minimum, these should have a very clear warning to this effect, and applications should be encouraged to get a ZKConnection and then make asynchronous calls on that. > Client library reconnecting breaks FIFO client order > > > Key: ZOOKEEPER-2619 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2619 > Project: ZooKeeper > Issue Type: Bug >Reporter: Diego Ongaro > > According to the USENIX ATC 2010 > [paper|https://www.use
[jira] [Commented] (ZOOKEEPER-2618) fix ClassNotFoundException on shutdown of client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603037#comment-15603037 ] wu wen commented on ZOOKEEPER-2618: --- Yes, this is the same problem, I just try to create a subtask to fix it. > fix ClassNotFoundException on shutdown of client > > > Key: ZOOKEEPER-2618 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2618 > Project: ZooKeeper > Issue Type: Sub-task > Components: java client >Affects Versions: 3.4.9 >Reporter: wu wen >Priority: Minor > Fix For: 3.4.10 > > Attachments: ZOOKEEPER-2618.patch > > > see ZOOKEEPER-1394,We also have this issue. > 2016-10-21 13:17:21.618 ERROR > localhost-startStop-1-SendThread(172.21.134.7:2005) ClientCnxn:414 - from > localhost-startStop-1-SendThread(172.21.134.7:2005) > java.lang.NoClassDefFoundError: org/apache/zookeeper/server/ZooTrace > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1128) > Caused by: java.lang.ClassNotFoundException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1315) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1178) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1139) > ... 1 more > Caused by: java.lang.IllegalStateException: Illegal access: this web > application instance has been stopped already. Could not load > [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown > for debugging purposes as well as to attempt to terminate the thread which > caused the illegal access. > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1325) > at > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1313) > ... 3 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-openjdk7 - Build # 1214 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1214/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 444080 lines...] [junit] at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:270) [junit] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:479) [junit] at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:203) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:201) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:151) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:315) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) [junit] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [junit] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [junit] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 20:42:12,097 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14159,name1=Connections,name2=127.0.0.1,name3=0x1000f98c8ac] [junit] 2016-10-24 20:42:12,197 [myid:] - INFO [main:ZooKeeper@1315] - Session: 0x1000f98c8ac closed [junit] 2016-10-24 20:42:12,197 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 56817 [junit] 2016-10-24 20:42:12,198 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 468 [junit] 2016-10-24 20:42:12,198 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2016-10-24 20:42:12,198 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2016-10-24 20:42:12,198 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2016-10-24 20:42:12,198 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:14159 [junit] 2016-10-24 20:42:12,198 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x1000f98c8ac [junit] 2016-10-24 20:42:12,199 [myid:] - INFO [main:ZooKeeperServer@529] - shutting down [junit] 2016-10-24 20:42:12,199 [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-24 20:42:12,199 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2016-10-24 20:42:12,199 [myid:] - INFO [main:PrepRequestProcessor@996] - Shutting down [junit] 2016-10-24 20:42:12,199 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2016-10-24 20:42:12,200 [myid:] - INFO [ProcessThread(sid:0 cport:14159)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2016-10-24 20:42:12,200 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2016-10-24 20:42:12,200 [myid:] - INFO [main:FinalRequestProcessor@481] - shutdown of request processor complete [junit] 2016-10-24 20:42:12,200 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14159,name1=InMemoryDataTree] [junit] 2016-10-24 20:42:12,200 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port14159] [junit] 2016-10-24 20:42:12,200 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 14159 [junit] 2016-10-24 20:42:12,201 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-10-24 20:42:12,204 [myid:] - INFO [main:ClientBase@568] - fdcount after test is: 1375 at start it was 1379 [junit] 2016-10-24 20:42:12,204 [myid:] - INFO [main:ZKTestCase$1@65] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2016-10-24 20:42:12,204 [myid:] - INFO [main:ZKTestCase$1@60] - FINISHED testWatcherAutoResetWithLocal [junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time el
[jira] [Created] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
Abraham Fine created ZOOKEEPER-2620: --- Summary: Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root Key: ZOOKEEPER-2620 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 Project: ZooKeeper Issue Type: Improvement Reporter: Abraham Fine Assignee: Abraham Fine testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes to file system permissions on ZooKeeper server startup. After debugging test failures [~hanm] was experiencing, we noticed that when the unit tests are run as root, these tests fail. We should have a comment to clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abraham Fine updated ZOOKEEPER-2620: Attachment: ZOOKEEPER-2620.patch > Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating > that the tests will fail when run as root > -- > > Key: ZOOKEEPER-2620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Abraham Fine >Assignee: Abraham Fine > Attachments: ZOOKEEPER-2620.patch > > > testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes > to file system permissions on ZooKeeper server startup. > After debugging test failures [~hanm] was experiencing, we noticed that when > the unit tests are run as root, these tests fail. We should have a comment to > clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abraham Fine updated ZOOKEEPER-2620: Attachment: ZOOKEEPER-2620.patch-br3.4 > Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating > that the tests will fail when run as root > -- > > Key: ZOOKEEPER-2620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Abraham Fine >Assignee: Abraham Fine > Attachments: ZOOKEEPER-2620.patch, ZOOKEEPER-2620.patch-br3.4 > > > testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes > to file system permissions on ZooKeeper server startup. > After debugging test failures [~hanm] was experiencing, we noticed that when > the unit tests are run as root, these tests fail. We should have a comment to > clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603400#comment-15603400 ] Hadoop QA commented on ZOOKEEPER-2620: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12835019/ZOOKEEPER-2620.patch-br3.4 against trunk revision cef5978969bedfe066f903834a9ea4af6d508844. +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/3498//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3498//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3498//console This message is automatically generated. > Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating > that the tests will fail when run as root > -- > > Key: ZOOKEEPER-2620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Abraham Fine >Assignee: Abraham Fine > Attachments: ZOOKEEPER-2620.patch, ZOOKEEPER-2620.patch-br3.4 > > > testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes > to file system permissions on ZooKeeper server startup. > After debugging test failures [~hanm] was experiencing, we noticed that when > the unit tests are run as root, these tests fail. We should have a comment to > clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Success: ZOOKEEPER-2620 PreCommit Build #3498
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3498/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 437611 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/3498//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3498//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3498//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] afde105aeba356983bacb0c9401a23ecd397f1af 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: 20 minutes 1 second 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-2620 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
[jira] [Commented] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603428#comment-15603428 ] Michael Han commented on ZOOKEEPER-2620: +1, thanks [~abrahamfine]! > Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating > that the tests will fail when run as root > -- > > Key: ZOOKEEPER-2620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Abraham Fine >Assignee: Abraham Fine > Attachments: ZOOKEEPER-2620.patch, ZOOKEEPER-2620.patch-br3.4 > > > testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes > to file system permissions on ZooKeeper server startup. > After debugging test failures [~hanm] was experiencing, we noticed that when > the unit tests are run as root, these tests fail. We should have a comment to > clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Han updated ZOOKEEPER-2620: --- Component/s: tests > Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating > that the tests will fail when run as root > -- > > Key: ZOOKEEPER-2620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 > Project: ZooKeeper > Issue Type: Improvement > Components: tests >Affects Versions: 3.4.9, 3.5.2 >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2620.patch, ZOOKEEPER-2620.patch-br3.4 > > > testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes > to file system permissions on ZooKeeper server startup. > After debugging test failures [~hanm] was experiencing, we noticed that when > the unit tests are run as root, these tests fail. We should have a comment to > clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Han updated ZOOKEEPER-2620: --- Affects Version/s: 3.4.9 3.5.2 > Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating > that the tests will fail when run as root > -- > > Key: ZOOKEEPER-2620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 > Project: ZooKeeper > Issue Type: Improvement > Components: tests >Affects Versions: 3.4.9, 3.5.2 >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2620.patch, ZOOKEEPER-2620.patch-br3.4 > > > testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes > to file system permissions on ZooKeeper server startup. > After debugging test failures [~hanm] was experiencing, we noticed that when > the unit tests are run as root, these tests fail. We should have a comment to > clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2620) Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating that the tests will fail when run as root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Han updated ZOOKEEPER-2620: --- Fix Version/s: 3.5.3 3.4.10 > Add comments to testReadOnlySnapshotDir and testReadOnlyTxnLogDir indicating > that the tests will fail when run as root > -- > > Key: ZOOKEEPER-2620 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2620 > Project: ZooKeeper > Issue Type: Improvement > Components: tests >Affects Versions: 3.4.9, 3.5.2 >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2620.patch, ZOOKEEPER-2620.patch-br3.4 > > > testReadOnlySnapshotDir and testReadOnlyTxnLogDir test the impact of changes > to file system permissions on ZooKeeper server startup. > After debugging test failures [~hanm] was experiencing, we noticed that when > the unit tests are run as root, these tests fail. We should have a comment to > clarify this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk - Build # 3131 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk/3131/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 442949 lines...] [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 23:29:41,076 [myid:] - INFO [New I/O boss #9471:ClientCnxnSocketNetty@208] - channel is told closing [junit] 2016-10-24 23:29:41,076 [myid:127.0.0.1:27504] - INFO [main-SendThread(127.0.0.1:27504):ClientCnxn$SendThread@1231] - channel for sessionid 0x2008cbbf8a6 is lost, closing socket connection and attempting reconnect [junit] 2016-10-24 23:29:41,273 [myid:127.0.0.1:27507] - INFO [main-SendThread(127.0.0.1:27507):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:27507. Will not attempt to authenticate using SASL (unknown error) [junit] 2016-10-24 23:29:41,274 [myid:] - INFO [New I/O boss #9504:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {} [junit] java.net.ConnectException: Connection refused: 127.0.0.1/127.0.0.1:27507 [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) [junit] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [junit] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 23:29:41,274 [myid:] - WARN [New I/O boss #9504:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 0xb6a35058] EXCEPTION: java.net.ConnectException: Connection refused: 127.0.0.1/127.0.0.1:27507 [junit] java.net.ConnectException: Connection refused: 127.0.0.1/127.0.0.1:27507 [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) [junit] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [junit] at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) [junit] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [junit] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [junit] at java.lang.Thread.run(Thread.java:745) [junit] 2016-10-24 23:29:41,274 [myid:] - INFO [New I/O boss #9504:ClientCnxnSocketNetty@208] - channel is told closing [junit] 2016-10-24 23:29:41,274 [myid:127.0.0.1:27507] - INFO [main-SendThread(127.0.0.1:27507):ClientCnxn$SendThread@1231] - channel for sessionid 0x3008cbbf919 is lost, closing socket connection and attempting reconnect [junit] Running org.apache.zookeeper.server.quorum.Zab1_0Test in thread 3 [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec, Thread: 3, Class: org.apache.zookeeper.server.quorum.Zab1_0Test [junit] Test org.apache.zookeeper.server.quorum.Zab1_0Test FAILED (timeout) BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1322: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1207: Tests failed! Total time: 16 minutes 33 seconds Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE [WARNINGS] Skipping publisher since build result is FAILURE Archiving artifacts Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Recording fingerprints Setting JDK_1_7_LA
ZooKeeper_branch34 - Build # 1699 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34/1699/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 205592 lines...] [junit] 2016-10-25 00:40:37,221 [myid:] - INFO [main:ZooKeeperServer@497] - shutting down [junit] 2016-10-25 00:40:37,221 [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-25 00:40:37,221 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2016-10-25 00:40:37,221 [myid:] - INFO [main:PrepRequestProcessor@765] - Shutting down [junit] 2016-10-25 00:40:37,222 [myid:] - INFO [main:SyncRequestProcessor@208] - Shutting down [junit] 2016-10-25 00:40:37,222 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2016-10-25 00:40:37,222 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited! [junit] 2016-10-25 00:40:37,223 [myid:] - INFO [main:FinalRequestProcessor@402] - shutdown of request processor complete [junit] 2016-10-25 00:40:37,224 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2016-10-25 00:40:37,224 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2016-10-25 00:40:37,226 [myid:] - INFO [main:ClientBase@445] - STARTING server [junit] 2016-10-25 00:40:37,226 [myid:] - INFO [main:ClientBase@366] - CREATING server instance 127.0.0.1:11221 [junit] 2016-10-25 00:40:37,227 [myid:] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2016-10-25 00:40:37,227 [myid:] - INFO [main:ClientBase@341] - STARTING server instance 127.0.0.1:11221 [junit] 2016-10-25 00:40:37,228 [myid:] - INFO [main:ZooKeeperServer@173] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test5645544484163212827.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test5645544484163212827.junit.dir/version-2 [junit] 2016-10-25 00:40:37,233 [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-25 00:40:37,233 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2016-10-25 00:40:37,233 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - Accepted socket connection from /127.0.0.1:42819 [junit] 2016-10-25 00:40:37,234 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:42819 [junit] 2016-10-25 00:40:37,234 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2016-10-25 00:40:37,235 [myid:] - INFO [Thread-5:NIOServerCnxn@1008] - Closed socket connection for client /127.0.0.1:42819 (no session established for client) [junit] 2016-10-25 00:40:37,235 [myid:] - INFO [main:JMXEnv@229] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2016-10-25 00:40:37,237 [myid:] - INFO [main:JMXEnv@246] - expect:InMemoryDataTree [junit] 2016-10-25 00:40:37,238 [myid:] - INFO [main:JMXEnv@250] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2016-10-25 00:40:37,238 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2016-10-25 00:40:37,238 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2016-10-25 00:40:37,239 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 31153 [junit] 2016-10-25 00:40:37,239 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20 [junit] 2016-10-25 00:40:37,239 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota [junit] 2016-10-25 00:40:37,239 [myid:] - INFO [main:ClientBase@522] - tearDown starting [junit] 2016-10-25 00:40:37,300 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x157f9482340 closed [junit] 2016-10-25 00:40:37,301 [myid:] - INFO [main:ClientBase@492] - STOPPING server [junit] 2016-10-25 00:40:37,301 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for session: 0x157f9482340 [junit] 2016-10-25 00:40:37,301 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - NIOServerCnxn factory exited run method [junit] 2016-10-25 00:40:37,301 [myid:] - INFO
[jira] [Updated] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1045: Attachment: QuorumPeer Mutual Authentication Via Sasl Feature Doc - 2016-Sep-25.pdf Attached feature document describing the configurations and upgrade steps. Please refer the same for understanding the latest patch and I hope this would help to setup secure cluster for testing the patch. Appreciate feedback. Thanks [~hanm] for the offline reviews. > Support Quorum Peer mutual authentication via SASL > -- > > Key: ZOOKEEPER-1045 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045 > Project: ZooKeeper > Issue Type: New Feature > Components: quorum, security >Reporter: Eugene Koontz >Assignee: Rakesh R >Priority: Critical > Fix For: 3.4.10, 3.5.3 > > Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch, > 1045_failing_phunt.tar.gz, HOST_RESOLVER-ZK-1045.patch, QuorumPeer Mutual > Authentication Via Sasl Feature Doc - 2016-Sep-25.pdf, > TEST-org.apache.zookeeper.server.quorum.auth.QuorumAuthUpgradeTest.txt, > ZK-1045-test-case-failure-logs.zip, ZOOKEEPER-1045 Test Plan.pdf, > ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045TestValidationDesign.pdf, > org.apache.zookeeper.server.quorum.auth.QuorumAuthUpgradeTest.testRollingUpgrade.log > > > ZOOKEEPER-938 addresses mutual authentication between clients and servers. > This bug, on the other hand, is for authentication among quorum peers. > Hopefully much of the work done on SASL integration with Zookeeper for > ZOOKEEPER-938 can be used as a foundation for this enhancement. > Review board: https://reviews.apache.org/r/47354/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1045: Attachment: ZOOKEEPER-1045-br-3-4.patch Attached new patch with the following changes: # Renamed {{quorumcnxn.threads.size}} to {{quorum.cnxn.threads.size}} # Removed {{README.md}} from the patch as I attached feature doc pdf doc separately in jira # Replaced {{IOUtils.cleanup(LOG, sock)}} with simple {{sock.close();}} as java-1.6 shows compilation errors. > Support Quorum Peer mutual authentication via SASL > -- > > Key: ZOOKEEPER-1045 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045 > Project: ZooKeeper > Issue Type: New Feature > Components: quorum, security >Reporter: Eugene Koontz >Assignee: Rakesh R >Priority: Critical > Fix For: 3.4.10, 3.5.3 > > Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch, > 1045_failing_phunt.tar.gz, HOST_RESOLVER-ZK-1045.patch, QuorumPeer Mutual > Authentication Via Sasl Feature Doc - 2016-Sep-25.pdf, > TEST-org.apache.zookeeper.server.quorum.auth.QuorumAuthUpgradeTest.txt, > ZK-1045-test-case-failure-logs.zip, ZOOKEEPER-1045 Test Plan.pdf, > ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, > ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045TestValidationDesign.pdf, > org.apache.zookeeper.server.quorum.auth.QuorumAuthUpgradeTest.testRollingUpgrade.log > > > ZOOKEEPER-938 addresses mutual authentication between clients and servers. > This bug, on the other hand, is for authentication among quorum peers. > Hopefully much of the work done on SASL integration with Zookeeper for > ZOOKEEPER-938 can be used as a foundation for this enhancement. > Review board: https://reviews.apache.org/r/47354/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2619) Client library reconnecting breaks FIFO client order
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604093#comment-15604093 ] Benjamin Reed commented on ZOOKEEPER-2619: -- thanx diego, you did express well what i was trying to say. i also like your proposal. there are probably more details to work out, like how would it look for the C api? i like how it encapsulates nicely the relation between a sequence of operations, and your example does make a compelling argument for also including the sync api. do we have some applications that we can use to validate the api? it would be nice to validate the design before we standardize it. what i meant by "i think it's a good idea to document this issue in this jira" is that it's good that we have this jira to discuss the problem and potential solutions. > Client library reconnecting breaks FIFO client order > > > Key: ZOOKEEPER-2619 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2619 > Project: ZooKeeper > Issue Type: Bug >Reporter: Diego Ongaro > > According to the USENIX ATC 2010 > [paper|https://www.usenix.org/conference/usenix-atc-10/zookeeper-wait-free-coordination-internet-scale-systems], > ZooKeeper provides "FIFO client order: all requests from a given client are > executed in the order that they were sent by the client." I believe > applications written using the Java client library are unable to rely on this > guarantee, and any current application that does so is broken. Other client > libraries are also likely to be affected. > Consider this application, which is simplified from the algorithm described > on Page 4 (right column) of the paper: > {code} > zk = new ZooKeeper(...) > zk.createAsync("/data-23857", "...", callback) > zk.createSync("/pointer", "/data-23857") > {code} > Assume an empty ZooKeeper database to begin with and no other writers. > Applying the above definition, if the ZooKeeper database contains /pointer, > it must also contain /data-23857. > Now consider this series of unfortunate events: > {code} > zk = new ZooKeeper(...) > // The library establishes a TCP connection. > zk.createAsync("/data-23857", "...", callback) > // The library/kernel closes the TCP connection because it times out, and > // the create of /data-23857 is doomed to fail with ConnectionLoss. Suppose > // that it never reaches the server. > // The library establishes a new TCP connection. > zk.createSync("/pointer", "/data-23857") > // The create of /pointer succeeds. > {code} > That's the problem: subsequent operations get assigned to the new connection > and succeed, while earlier operations fail. > In general, I believe it's impossible to have a system with the following > three properties: > # FIFO client order for asynchronous operations, > # Failing operations when connections are lost, AND > # Transparently reconnecting when connections are lost. > To argue this, consider an application that issues a series of pipelined > operations, then upon noticing a connection loss, issues a series of recovery > operations, repeating the recovery procedure as necessary. If a pipelined > operation fails, all subsequent operations in the pipeline must also fail. > Yet the client must also carry on eventually: the recovery operations cannot > be trivially failed forever. Unfortunately, the client library does not know > where the pipelined operations end and the recovery operations begin. At the > time of a connection loss, subsequent pipelined operations may or may not be > queued in the library; others might be upcoming in the application thread. If > the library re-establishes a connection too early, it will send pipelined > operations out of FIFO client order. > I considered a possible workaround of having the client diligently check its > callbacks and watchers for connection loss events, and do its best to stop > the subsequent pipelined operations at the first sign of a connection loss. > In addition to being a large burden for the application, this does not solve > the problem all the time. In particular, if the callback thread is delayed > significantly (as can happen due to excessive computation or scheduling > hiccups), the application may not learn about the connection loss event until > after the connection has been re-established and after dependent pipelined > operations have already been transmitted over the new connection. > I suggest the following API changes to fix the problem: > - Add a method ZooKeeper.getConnection() returning a ZKConnection object. > ZKConnection would wrap a TCP connection. It would include all synchronous > and asynchronous operations currently defined on the ZooKeeper class. Upon a > connection loss on a ZKConnection, all subsequent operations on t
Re: Review Request 47354: ZOOKEEPER-1045 : Quorum mutual authentication using SASL mechanism
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/47354/ --- (Updated Oct. 25, 2016, 5:05 a.m.) Review request for zookeeper, fpj, Ivan Kelly, Patrick Hunt, and Raul Gutierrez Segales. Changes --- New patch contains the following changes: Renamed quorumcnxn.threads.size to quorum.cnxn.threads.size Removed README.md from the patch as I attached feature doc pdf doc separately in jira Replaced IOUtils.cleanup(LOG, sock) with simple sock.close(); as java-1.6 shows compilation errors. Bugs: ZOOKEEPER-1045 https://issues.apache.org/jira/browse/ZOOKEEPER-1045 Repository: zookeeper-git Description --- Quorum mutual authentication using SASL mechanism - Digest/Kerberos Diffs (updated) - build.xml 505597a ivy.xml 95b0e5a src/java/main/org/apache/zookeeper/Login.java aaa220c src/java/main/org/apache/zookeeper/SaslClientCallbackHandler.java PRE-CREATION src/java/main/org/apache/zookeeper/client/ZooKeeperSaslClient.java 21ef0fa src/java/main/org/apache/zookeeper/server/ZooKeeperSaslServer.java 71870ce src/java/main/org/apache/zookeeper/server/auth/SaslServerCallbackHandler.java 7fdffde src/java/main/org/apache/zookeeper/server/quorum/Follower.java 043a522 src/java/main/org/apache/zookeeper/server/quorum/Leader.java c83d352 src/java/main/org/apache/zookeeper/server/quorum/Learner.java 647b8a2 src/java/main/org/apache/zookeeper/server/quorum/LearnerHandler.java 8a748c7 src/java/main/org/apache/zookeeper/server/quorum/Observer.java e53f6f2 src/java/main/org/apache/zookeeper/server/quorum/QuorumCnxManager.java 20e5f16 src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java 2f0f21b src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerConfig.java 0924ef6 src/java/main/org/apache/zookeeper/server/quorum/QuorumPeerMain.java e9c8007 src/java/main/org/apache/zookeeper/server/quorum/auth/NullQuorumAuthLearner.java PRE-CREATION src/java/main/org/apache/zookeeper/server/quorum/auth/NullQuorumAuthServer.java PRE-CREATION src/java/main/org/apache/zookeeper/server/quorum/auth/QuorumAuth.java PRE-CREATION src/java/main/org/apache/zookeeper/server/quorum/auth/QuorumAuthLearner.java PRE-CREATION src/java/main/org/apache/zookeeper/server/quorum/auth/QuorumAuthServer.java PRE-CREATION src/java/main/org/apache/zookeeper/server/quorum/auth/SaslQuorumAuthLearner.java PRE-CREATION src/java/main/org/apache/zookeeper/server/quorum/auth/SaslQuorumAuthServer.java PRE-CREATION src/java/main/org/apache/zookeeper/server/quorum/auth/SaslQuorumServerCallbackHandler.java PRE-CREATION src/java/main/org/apache/zookeeper/util/SecurityUtils.java PRE-CREATION src/java/test/data/kerberos/minikdc-krb5.conf PRE-CREATION src/java/test/data/kerberos/minikdc.ldiff PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/CnxManagerTest.java 8db7fa8 src/java/test/org/apache/zookeeper/server/quorum/FLEBackwardElectionRoundTest.java c1259d1 src/java/test/org/apache/zookeeper/server/quorum/FLECompatibilityTest.java 72e4fc9 src/java/test/org/apache/zookeeper/server/quorum/FLEDontCareTest.java a4c0cb0 src/java/test/org/apache/zookeeper/server/quorum/FLELostMessageTest.java 39a53ca src/java/test/org/apache/zookeeper/server/quorum/LearnerTest.java 2ae57ce src/java/test/org/apache/zookeeper/server/quorum/QuorumCnxManagerTest.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/QuorumPeerTestBase.java 85817b2 src/java/test/org/apache/zookeeper/server/quorum/Zab1_0Test.java ab8ce42 src/java/test/org/apache/zookeeper/server/quorum/auth/KerberosSecurityTestcase.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/KerberosTestUtils.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/MiniKdc.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/MiniKdcTest.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/QuorumAuthTestBase.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/QuorumAuthUpgradeTest.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/QuorumDigestAuthTest.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/QuorumKerberosAuthTest.java PRE-CREATION src/java/test/org/apache/zookeeper/server/quorum/auth/QuorumKerberosHostBasedAuthTest.java PRE-CREATION src/java/test/org/apache/zookeeper/test/FLEPredicateTest.java 8088505 src/zookeeper.jute 6521e54 Diff: https://reviews.apache.org/r/47354/diff/ Testing --- Added unit test cases to verify the changes. Thanks, Rakesh R
Re: Test plan for ZK-1045 - Call for volunteers
I've uploaded feature document to the ZOOKEEPER-1045 jira, link => https://goo.gl/cvzG8A. I hope this doc will help you to setup a secured zk cluster and start testing the feature. It would be really great to see the test/review/usability feedback. Thanks! Rakesh On Fri, Oct 21, 2016 at 8:04 PM, Flavio Junqueira wrote: > Michael Han posted an update to the test plan to the jira and I want to > call the attention of the community to it. It is a big change that we need > to be extra careful about because it is supposed to go to the 3.4 branch. > It'd be great to have more folks in the community involved with the > testing. If you have cycles and interest, please help with testing. > > -Flavio
[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604278#comment-15604278 ] Alexander Shraer commented on ZOOKEEPER-2556: - Hi, thanks for the patch! I have only one suggestion. Instead of a new separate test for peerType, perhaps you could add a few more lines to one of the existing tests. Looking at this again perhaps the best one would be testConfigFileBackwardCompatibility() where it already checks that "server." and "clientPort" are being removed, you could add that "peerType" is also being removed. Alex > 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)