ZooKeeper_branch35_solaris - Build # 390 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_solaris/390/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 467157 lines...] [junit] 2017-01-10 01:48:48,476 [myid:] - INFO [main:ClientBase@386] - CREATING server instance 127.0.0.1:11222 [junit] 2017-01-10 01:48:48,476 [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] 2017-01-10 01:48:48,477 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2017-01-10 01:48:48,478 [myid:] - INFO [main:ClientBase@361] - STARTING server instance 127.0.0.1:11222 [junit] 2017-01-10 01:48:48,478 [myid:] - INFO [main:ZooKeeperServer@893] - minSessionTimeout set to 6000 [junit] 2017-01-10 01:48:48,478 [myid:] - INFO [main:ZooKeeperServer@902] - maxSessionTimeout set to 6 [junit] 2017-01-10 01:48:48,479 [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/test5408114099250741631.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test5408114099250741631.junit.dir/version-2 [junit] 2017-01-10 01:48:48,479 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test5408114099250741631.junit.dir/version-2/snapshot.b [junit] 2017-01-10 01:48:48,481 [myid:] - INFO [main:FileTxnSnapLog@320] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test5408114099250741631.junit.dir/version-2/snapshot.b [junit] 2017-01-10 01:48:48,482 [myid:] - ERROR [main:ZooKeeperServer@505] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-10 01:48:48,483 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2017-01-10 01:48:48,483 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:63132 [junit] 2017-01-10 01:48:48,484 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:63132 [junit] 2017-01-10 01:48:48,484 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2017-01-10 01:48:48,484 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:63132 (no session established for client) [junit] 2017-01-10 01:48:48,484 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2017-01-10 01:48:48,486 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2017-01-10 01:48:48,486 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2017-01-10 01:48:48,486 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2017-01-10 01:48:48,486 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2017-01-10 01:48:48,486 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 18008 [junit] 2017-01-10 01:48:48,487 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2017-01-10 01:48:48,487 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2017-01-10 01:48:48,487 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2017-01-10 01:48:48,562 [myid:] - INFO [main:ZooKeeper@1322] - Session: 0x1260309b8d2 closed [junit] 2017-01-10 01:48:48,562 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x1260309b8d2 [junit] 2017-01-10 01:48:48,562 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2017-01-10 01:48:48,562 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2017-01-10 01:48:48,562 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2017-01-10 01:48:48,562 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactor
ZooKeeper-trunk-jdk8 - Build # 894 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/894/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 452507 lines...] [junit] 2017-01-10 00:22:55,765 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1231] - Unable to read additional data from server sessionid 0x102196a73d9, likely server has closed socket, closing socket connection and attempting reconnect [junit] 2017-01-10 00:22:55,777 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:11222. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-10 00:22:55,777 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@948] - Socket connection established, initiating session, client: /127.0.0.1:58127, server: 127.0.0.1/127.0.0.1:11222 [junit] 2017-01-10 00:22:55,777 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:/127.0.0.1:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:58127 [junit] 2017-01-10 00:22:55,777 [myid:] - WARN [NIOWorkerThread-8:NIOServerCnxn@369] - Exception causing close of session 0x0: ZooKeeperServer not running [junit] 2017-01-10 00:22:55,778 [myid:] - INFO [NIOWorkerThread-8:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:58127 (no session established for client) [junit] 2017-01-10 00:22:55,778 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1231] - Unable to read additional data from server sessionid 0x102196a73d90001, likely server has closed socket, closing socket connection and attempting reconnect [junit] 2017-01-10 00:22:57,361 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:11222. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-10 00:22:57,361 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@948] - Socket connection established, initiating session, client: /127.0.0.1:58181, server: 127.0.0.1/127.0.0.1:11222 [junit] 2017-01-10 00:22:57,362 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:/127.0.0.1:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:58181 [junit] 2017-01-10 00:22:57,362 [myid:] - WARN [NIOWorkerThread-9:NIOServerCnxn@369] - Exception causing close of session 0x0: ZooKeeperServer not running [junit] 2017-01-10 00:22:57,362 [myid:] - INFO [NIOWorkerThread-9:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:58181 (no session established for client) [junit] 2017-01-10 00:22:57,362 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1231] - Unable to read additional data from server sessionid 0x102196a73d9, likely server has closed socket, closing socket connection and attempting reconnect [junit] 2017-01-10 00:22:57,601 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:11222. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-10 00:22:57,602 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@948] - Socket connection established, initiating session, client: /127.0.0.1:58190, server: 127.0.0.1/127.0.0.1:11222 [junit] 2017-01-10 00:22:57,602 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:/127.0.0.1:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:58190 [junit] 2017-01-10 00:22:57,602 [myid:] - WARN [NIOWorkerThread-10:NIOServerCnxn@369] - Exception causing close of session 0x0: ZooKeeperServer not running [junit] 2017-01-10 00:22:57,602 [myid:] - INFO [NIOWorkerThread-10:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:58190 (no session established for client) [junit] 2017-01-10 00:22:57,602 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1231] - Unable to read additional data from server sessionid 0x102196a73d90001, likely server has closed socket, closing socket connection and attempting reconnect [junit] 2017-01-10 00:22:59,286 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:11222. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-10 00:22:59,286 [myid:127.0.0.1:11222] - INFO [main-SendThread(127.0.0.1:11222):ClientCnxn$SendThread@948] - Socket connection established, initiating session, client: /127.
ZooKeeper-trunk-solaris - Build # 1459 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1459/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 470707 lines...] [junit] 2017-01-09 23:23:55,330 [myid:] - INFO [main:ClientBase@386] - CREATING server instance 127.0.0.1:11222 [junit] 2017-01-09 23:23:55,330 [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] 2017-01-09 23:23:55,331 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2017-01-09 23:23:55,332 [myid:] - INFO [main:ClientBase@361] - STARTING server instance 127.0.0.1:11222 [junit] 2017-01-09 23:23:55,332 [myid:] - INFO [main:ZooKeeperServer@894] - minSessionTimeout set to 6000 [junit] 2017-01-09 23:23:55,332 [myid:] - INFO [main:ZooKeeperServer@903] - maxSessionTimeout set to 6 [junit] 2017-01-09 23:23:55,332 [myid:] - INFO [main:ZooKeeperServer@160] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7034903042188136746.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7034903042188136746.junit.dir/version-2 [junit] 2017-01-09 23:23:55,333 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7034903042188136746.junit.dir/version-2/snapshot.b [junit] 2017-01-09 23:23:55,335 [myid:] - INFO [main:FileTxnSnapLog@320] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7034903042188136746.junit.dir/version-2/snapshot.b [junit] 2017-01-09 23:23:55,337 [myid:] - ERROR [main:ZooKeeperServer@506] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-09 23:23:55,337 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2017-01-09 23:23:55,337 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:44159 [junit] 2017-01-09 23:23:55,338 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:44159 [junit] 2017-01-09 23:23:55,338 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2017-01-09 23:23:55,338 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:44159 (no session established for client) [junit] 2017-01-09 23:23:55,338 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2017-01-09 23:23:55,340 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2017-01-09 23:23:55,340 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2017-01-09 23:23:55,340 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2017-01-09 23:23:55,340 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2017-01-09 23:23:55,340 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17916 [junit] 2017-01-09 23:23:55,341 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2017-01-09 23:23:55,341 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2017-01-09 23:23:55,341 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2017-01-09 23:23:55,412 [myid:] - INFO [main:ZooKeeper@1324] - Session: 0x12602851330 closed [junit] 2017-01-09 23:23:55,412 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2017-01-09 23:23:55,412 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x12602851330 [junit] 2017-01-09 23:23:55,412 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2017-01-09 23:23:55,412 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2017-01-09 23:23:55,412 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@4
[jira] [Commented] (ZOOKEEPER-2511) Implement AutoCloseable in ZooKeeper.java
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813066#comment-15813066 ] Hudson commented on ZOOKEEPER-2511: --- SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #3230 (See [https://builds.apache.org/job/ZooKeeper-trunk/3230/]) ZOOKEEPER-2511: Implement AutoCloseable in ZooKeeper.java (hanm: rev c2434883dcdd85450ac73b7e69f3deed83fa5bf4) * (edit) src/java/test/org/apache/zookeeper/test/ClientTest.java * (edit) src/java/main/org/apache/zookeeper/ZooKeeper.java > Implement AutoCloseable in ZooKeeper.java > - > > Key: ZOOKEEPER-2511 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2511 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2511.patch > > > As a java developer I would like to be able to use try-with-resource blocks > with ZooKeeper objects in order to make closing sessions easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ZOOKEEPER-2658) Trunk / branch-3.5 build broken.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han resolved ZOOKEEPER-2658.
Resolution: Fixed
Fix Version/s: 3.6.0
3.5.3
3.4.10
Fixed by updating Jenkins job to use new JDK installation (jdk-1.7.0_79 -
unlimited security).
> Trunk / branch-3.5 build broken.
>
>
> Key: ZOOKEEPER-2658
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2658
> Project: ZooKeeper
> Issue Type: Task
>Affects Versions: 3.5.2, 3.6.0
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Critical
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/
> https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/
> The trunk build is broken for over two weeks. It is likely caused by
> Infrastructure issues.
> {noformat}
> [ZooKeeper-trunk-openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant
> -Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml
> -Djavac.target=1.7 clean test-core-java
> Error: JAVA_HOME is not defined correctly.
> We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
> Build step 'Invoke Ant' marked build as failure
> 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
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper_branch35_openjdk7 - Build # 367 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/367/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 484846 lines...] [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-01-09 22:09:09,233 [myid:127.0.0.1:19430] - INFO [main-SendThread(127.0.0.1:19430):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:19430. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-09 22:09:09,233 [myid:127.0.0.1:19430] - WARN [main-SendThread(127.0.0.1:19430):ClientCnxn$SendThread@1235] - Session 0x301456ecceb for server 127.0.0.1/127.0.0.1:19430, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-01-09 22:09:09,637 [myid:127.0.0.1:19424] - INFO [main-SendThread(127.0.0.1:19424):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:19424. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-09 22:09:09,638 [myid:127.0.0.1:19424] - WARN [main-SendThread(127.0.0.1:19424):ClientCnxn$SendThread@1235] - Session 0x101456eccd5 for server 127.0.0.1/127.0.0.1:19424, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-01-09 22:09:09,699 [myid:] - INFO [ProcessThread(sid:0 cport:19547)::PrepRequestProcessor@656] - Processed session termination for sessionid: 0x1014571ddcd [junit] 2017-01-09 22:09:09,702 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port19547,name1=Connections,name2=127.0.0.1,name3=0x1014571ddcd] [junit] 2017-01-09 22:09:09,702 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x1014571ddcd [junit] 2017-01-09 22:09:09,702 [myid:] - INFO [main:ZooKeeper@1322] - Session: 0x1014571ddcd closed [junit] 2017-01-09 22:09:09,703 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 100620 [junit] 2017-01-09 22:09:09,703 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 467 [junit] 2017-01-09 22:09:09,703 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2017-01-09 22:09:09,703 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2017-01-09 22:09:09,704 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2017-01-09 22:09:09,704 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:19547 [junit] 2017-01-09 22:09:09,709 [myid:] - INFO [main:ZooKeeperServer@533] - shutting down [junit] 2017-01-09 22:09:09,710 [myid:] - ERROR [main:ZooKeeperServer@505] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-09 22:09:09,710 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2017-01-09 22:09:09,710 [myid:] - INFO [main:PrepRequestProcessor@974] - Shutting down [junit] 2017-01-09 22:09:09,710 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2017-01-09 22:09:09,710 [myid:] - INFO [ProcessThread(sid:0 cport:19547)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop! [junit] 2017-01-09 22:09:09,710 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2017-01-09 22:09:09,711 [myid:] - INFO [main:FinalRequestProcessor@479] - shutdown of request processor complete [junit] 2017-01-09 22:09:09,711 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port19547,name1=InMemor
[jira] [Commented] (ZOOKEEPER-2511) Implement AutoCloseable in ZooKeeper.java
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812960#comment-15812960 ] ASF GitHub Bot commented on ZOOKEEPER-2511: --- Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/143 > Implement AutoCloseable in ZooKeeper.java > - > > Key: ZOOKEEPER-2511 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2511 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2511.patch > > > As a java developer I would like to be able to use try-with-resource blocks > with ZooKeeper objects in order to make closing sessions easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zookeeper pull request #143: ZOOKEEPER-2511: Implement AutoCloseable in ZooK...
Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/143 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
ZooKeeper-trunk-openjdk7 - Build # 1316 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1316/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H17 (ubuntu) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress
> git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision c2434883dcdd85450ac73b7e69f3deed83fa5bf4
(refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f c2434883dcdd85450ac73b7e69f3deed83fa5bf4
> git rev-list 7c51b01e89acb38165553366f7e3b2a46c00aa27 # timeout=10
No emails were triggered.
[ZooKeeper-trunk-openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml
-Djavac.target=1.7 clean test-core-java
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
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.
Failed: ZOOKEEPER- PreCommit Build #197
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/197/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 30 lines...] at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to H7(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:781) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at com.sun.proxy.$Proxy90.checkoutBranch(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327) at com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:984) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1087) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: hudson.plugins.git.GitException: Command "git checkout -f origin/trunk" returned status code 1: stdout: stderr: error: pathspec 'origin/trunk' did not match any file(s) known to git. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1699) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1695) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1317) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1329) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1979) at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:884) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:859) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:818) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Archiving artifacts Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? [description-setter] Could not determine description. Putting comment on the pull request Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2511) Implement AutoCloseable in ZooKeeper.java
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812952#comment-15812952 ] ASF GitHub Bot commented on ZOOKEEPER-2511: --- Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/143 LGTM, merging, thanks @afine. > Implement AutoCloseable in ZooKeeper.java > - > > Key: ZOOKEEPER-2511 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2511 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 3.5.3 > > Attachments: ZOOKEEPER-2511.patch > > > As a java developer I would like to be able to use try-with-resource blocks > with ZooKeeper objects in order to make closing sessions easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zookeeper issue #143: ZOOKEEPER-2511: Implement AutoCloseable in ZooKeeper.j...
Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/143 LGTM, merging, thanks @afine. --- 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. ---
Re: Crash on detecting a corruption
>> Why does ZooKeeper not fix the corrupted entry automatically using replicas? What is the reason for this design decision? My view on this is the decision of repair or not might not be always applicable in any cases - in some cases such as hardware failures it is better to crashing stop and have admin intervene (i.e. by reconfiguring the cluster) than prematurely trying to repair autonomously which would not succeed due to hardware failure, and worse proceeding on top of such failures might compromise the safety properties ZooKeeper promised. Crashing immediately sacrifice liveness to certain extent (if the quorum fails to form by taking out the failed node), but kept the safety property. Another benefit of crashing immediately is this could greatly simplify the system model and behavior to reason about, for applications / management layers built on top of ZK. On the other side in some cases it might be totally reasonable to try performing a repair and I remember there are some ZooKeeper JIRAs describing such best-effort based action. But in general since ZooKeeper does not deal with Byzantine Faults, it might not always be applicable for such repair attempts. On Mon, Jan 9, 2017 at 9:41 AM, Edward Ribeiro wrote: > Hi, > > I am not aware if this was a design decision, to be honest. AFAIK, this has > been a long standing bug. :( I have compiled a handful of JIRA issues that > are basically this problem scattered through multiple repetitive issues. > Gonna aggregate them soon, I hope. We, the community, should raise the > priority and tackle this issue to make ZK server more resilient and robust > in the face of logs/txn files corruption. Any suggestion is more than > welcome, by the way! > > Cheers, > Eddie > > > On Fri, Jan 6, 2017 at 6:38 PM, Aishwarya Ganesan > wrote: > > > Hi, > > > > We are looking at how ZooKeeper handles silent data corruptions resulting > > from underlying problems in disks and file systems atop them [1,2]. > > > > We set up a 3-node ZooKeeper cluster and introduce silent data > corruptions > > to different blocks in the on-disk files. In all the cases, ZooKeeper is > > able to detect corruptions in the log file using checksums. > > > > However, on detecting a corruption, the ZooKeeper node in which > corruption > > occurred crashes instead of trying to fix the corrupted data > automatically > > using the replicas. Why does ZooKeeper not fix the corrupted entry > > automatically using replicas? What is the reason for this design > decision? > > It would be helpful if anyone could give some insights on this. > > > > [1] https://research.cs.wisc.edu/wind/Publications/zfs- > > corruption-fast10.pdf > > [2] http://www.cs.toronto.edu/~bianca/papers/fast08.pdf > > > > Thanks, > > Aishwarya > > > -- Cheers Michael.
ZooKeeper-trunk-openjdk7 - Build # 1315 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1315/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H13 (ubuntu) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7
Cloning the remote Git repository
Cloning repository git://git.apache.org/zookeeper.git
> git init /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7 #
> timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress
> git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* #
> timeout=10
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git -c core.askpass=true fetch --tags --progress
> git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 7c51b01e89acb38165553366f7e3b2a46c00aa27
(refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7c51b01e89acb38165553366f7e3b2a46c00aa27
> git rev-list 7c51b01e89acb38165553366f7e3b2a46c00aa27 # timeout=10
No emails were triggered.
[ZooKeeper-trunk-openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml
-Djavac.target=1.7 clean test-core-java
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
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-2511) Implement AutoCloseable in ZooKeeper.java
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812513#comment-15812513
]
ASF GitHub Bot commented on ZOOKEEPER-2511:
---
Github user afine commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/143#discussion_r95219646
--- Diff: src/java/main/org/apache/zookeeper/ZooKeeper.java ---
@@ -127,7 +127,13 @@
* EventNone and state sKeeperStateDisconnected.
*
*/
-public class ZooKeeper {
+// We suppress the "try" warning here because the close() method's
signature
--- End diff --
agreed, let me know if the changes address your concerns @eribeiro @hanm
> Implement AutoCloseable in ZooKeeper.java
> -
>
> Key: ZOOKEEPER-2511
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2511
> Project: ZooKeeper
> Issue Type: Improvement
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Fix For: 3.5.3
>
> Attachments: ZOOKEEPER-2511.patch
>
>
> As a java developer I would like to be able to use try-with-resource blocks
> with ZooKeeper objects in order to make closing sessions easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] zookeeper pull request #143: ZOOKEEPER-2511: Implement AutoCloseable in ZooK...
Github user afine commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/143#discussion_r95219646
--- Diff: src/java/main/org/apache/zookeeper/ZooKeeper.java ---
@@ -127,7 +127,13 @@
* EventNone and state sKeeperStateDisconnected.
*
*/
-public class ZooKeeper {
+// We suppress the "try" warning here because the close() method's
signature
--- End diff --
agreed, let me know if the changes address your concerns @eribeiro @hanm
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
Failed: ZOOKEEPER- PreCommit Build #196
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/196/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 25 lines...]
Getting sizes
Done: 14
Compressing objects
Done: 0
Writing objects
Done: 15
remote: Updating references
Merging refs/tags/changes/196
> git rev-parse refs/tags/changes/196^{commit} # timeout=10
> git merge 5a7a36d25276c873b422db210106fba0fe61b74c # timeout=10
> git rev-parse branch-3.5^{commit} # timeout=10
Checking out Revision 66fc2c6e8421d3f6ac0e0bfb8397d270dc352bc6 (branch-3.5)
> git config core.sparsecheckout # timeout=10
> git checkout -f 66fc2c6e8421d3f6ac0e0bfb8397d270dc352bc6
> git rev-parse origin/branch-3.5^{commit} # timeout=10
> git rev-list 3cdaeedf8b59da50421c5b6bba1d3f72dcfdd661 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash
/tmp/hudson2756694215573975565.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 10240
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Buildfile:
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml
BUILD FAILED
Target "qa-test-pullrequest" does not exist in the project "ZooKeeper".
Total time: 0 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?
[description-setter] Could not determine description.
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
###
## FAILED TESTS (if any)
##
No tests ran.
Re: Crash on detecting a corruption
Hi, I am not aware if this was a design decision, to be honest. AFAIK, this has been a long standing bug. :( I have compiled a handful of JIRA issues that are basically this problem scattered through multiple repetitive issues. Gonna aggregate them soon, I hope. We, the community, should raise the priority and tackle this issue to make ZK server more resilient and robust in the face of logs/txn files corruption. Any suggestion is more than welcome, by the way! Cheers, Eddie On Fri, Jan 6, 2017 at 6:38 PM, Aishwarya Ganesan wrote: > Hi, > > We are looking at how ZooKeeper handles silent data corruptions resulting > from underlying problems in disks and file systems atop them [1,2]. > > We set up a 3-node ZooKeeper cluster and introduce silent data corruptions > to different blocks in the on-disk files. In all the cases, ZooKeeper is > able to detect corruptions in the log file using checksums. > > However, on detecting a corruption, the ZooKeeper node in which corruption > occurred crashes instead of trying to fix the corrupted data automatically > using the replicas. Why does ZooKeeper not fix the corrupted entry > automatically using replicas? What is the reason for this design decision? > It would be helpful if anyone could give some insights on this. > > [1] https://research.cs.wisc.edu/wind/Publications/zfs- > corruption-fast10.pdf > [2] http://www.cs.toronto.edu/~bianca/papers/fast08.pdf > > Thanks, > Aishwarya >
ZooKeeper_branch35_solaris - Build # 389 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_solaris/389/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 479924 lines...] [junit] 2017-01-09 17:17:00,130 [myid:] - INFO [main:ClientBase@386] - CREATING server instance 127.0.0.1:11222 [junit] 2017-01-09 17:17:00,130 [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] 2017-01-09 17:17:00,131 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2017-01-09 17:17:00,131 [myid:] - INFO [main:ClientBase@361] - STARTING server instance 127.0.0.1:11222 [junit] 2017-01-09 17:17:00,132 [myid:] - INFO [main:ZooKeeperServer@893] - minSessionTimeout set to 6000 [junit] 2017-01-09 17:17:00,132 [myid:] - INFO [main:ZooKeeperServer@902] - maxSessionTimeout set to 6 [junit] 2017-01-09 17:17:00,132 [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/test2359032321446118501.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test2359032321446118501.junit.dir/version-2 [junit] 2017-01-09 17:17:00,133 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test2359032321446118501.junit.dir/version-2/snapshot.b [junit] 2017-01-09 17:17:00,135 [myid:] - INFO [main:FileTxnSnapLog@320] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test2359032321446118501.junit.dir/version-2/snapshot.b [junit] 2017-01-09 17:17:00,136 [myid:] - ERROR [main:ZooKeeperServer@505] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-09 17:17:00,136 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2017-01-09 17:17:00,137 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:57538 [junit] 2017-01-09 17:17:00,137 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:57538 [junit] 2017-01-09 17:17:00,137 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2017-01-09 17:17:00,138 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:57538 (no session established for client) [junit] 2017-01-09 17:17:00,138 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2017-01-09 17:17:00,139 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2017-01-09 17:17:00,139 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2017-01-09 17:17:00,139 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2017-01-09 17:17:00,140 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2017-01-09 17:17:00,140 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17885 [junit] 2017-01-09 17:17:00,140 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2017-01-09 17:17:00,140 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2017-01-09 17:17:00,140 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2017-01-09 17:17:00,222 [myid:] - INFO [main:ZooKeeper@1311] - Session: 0x12601352612 closed [junit] 2017-01-09 17:17:00,222 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x12601352612 [junit] 2017-01-09 17:17:00,222 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2017-01-09 17:17:00,222 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2017-01-09 17:17:00,223 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2017-01-09 17:17:00,223 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactor
[jira] [Commented] (ZOOKEEPER-2368) Client watches are not disconnected on close
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812277#comment-15812277 ] Timothy Ward commented on ZOOKEEPER-2368: - I don't personally think that it's necessary to add an extra close method, as there's no breaking change for existing watchers. I'm happy to bow to the ZooKeeper team's superior experience though. > Client watches are not disconnected on close > > > Key: ZOOKEEPER-2368 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2368 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.0, 3.5.0 >Reporter: Timothy Ward >Assignee: Timothy Ward > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2368.patch > > > If I have a ZooKeeper client connected to an ensemble then obviously I can > register watches. > If the client is disconnected (for example by a failing ensemble member) then > I get a disconnection event for all of my watches. If, on the other hand, my > client is closed then I *do not* get a disconnection event. This asymmetry > makes it really hard to clear up properly when using the asynchronous API, as > there is no way to "fail" data reads/updates when the client is closed. > I believe that the correct behaviour should be for all watchers to receive a > disconnection event when the client is closed. The watchers can then respond > as appropriate, and can differentiate between a "server disconnect" and a > "client disconnect" by checking the ZooKeeper#getState() method. > This would not be a breaking behaviour change as Watchers are already > required to handle disconnection events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2368) Client watches are not disconnected on close
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812267#comment-15812267 ] Jordan Zimmerman commented on ZOOKEEPER-2368: - [~timothyjward] - how about an alternate close() that has a flag to control this behavior? > Client watches are not disconnected on close > > > Key: ZOOKEEPER-2368 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2368 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.0, 3.5.0 >Reporter: Timothy Ward >Assignee: Timothy Ward > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2368.patch > > > If I have a ZooKeeper client connected to an ensemble then obviously I can > register watches. > If the client is disconnected (for example by a failing ensemble member) then > I get a disconnection event for all of my watches. If, on the other hand, my > client is closed then I *do not* get a disconnection event. This asymmetry > makes it really hard to clear up properly when using the asynchronous API, as > there is no way to "fail" data reads/updates when the client is closed. > I believe that the correct behaviour should be for all watchers to receive a > disconnection event when the client is closed. The watchers can then respond > as appropriate, and can differentiate between a "server disconnect" and a > "client disconnect" by checking the ZooKeeper#getState() method. > This would not be a breaking behaviour change as Watchers are already > required to handle disconnection events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2368) Client watches are not disconnected on close
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812264#comment-15812264 ] Jordan Zimmerman commented on ZOOKEEPER-2368: - Sure, that's reasonable. > Client watches are not disconnected on close > > > Key: ZOOKEEPER-2368 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2368 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.0, 3.5.0 >Reporter: Timothy Ward >Assignee: Timothy Ward > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2368.patch > > > If I have a ZooKeeper client connected to an ensemble then obviously I can > register watches. > If the client is disconnected (for example by a failing ensemble member) then > I get a disconnection event for all of my watches. If, on the other hand, my > client is closed then I *do not* get a disconnection event. This asymmetry > makes it really hard to clear up properly when using the asynchronous API, as > there is no way to "fail" data reads/updates when the client is closed. > I believe that the correct behaviour should be for all watchers to receive a > disconnection event when the client is closed. The watchers can then respond > as appropriate, and can differentiate between a "server disconnect" and a > "client disconnect" by checking the ZooKeeper#getState() method. > This would not be a breaking behaviour change as Watchers are already > required to handle disconnection events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2368) Client watches are not disconnected on close
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811936#comment-15811936 ] Timothy Ward commented on ZOOKEEPER-2368: - I'm not sure that I agree with this. If the ZooKeeper handle is already disconnected (e.g. due to a network failure) before it is closed then the session may not actually be expired when the handle is closed. If the session timeout is a long one it is perfectly possible that a client could be recreated and re-attach to the previous session. The one thing that is absolutely guaranteed on a call to close is that the ZooKeeper handle is disconnected, hence I proposed using that KeeperState. > Client watches are not disconnected on close > > > Key: ZOOKEEPER-2368 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2368 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.4.0, 3.5.0 >Reporter: Timothy Ward >Assignee: Timothy Ward > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2368.patch > > > If I have a ZooKeeper client connected to an ensemble then obviously I can > register watches. > If the client is disconnected (for example by a failing ensemble member) then > I get a disconnection event for all of my watches. If, on the other hand, my > client is closed then I *do not* get a disconnection event. This asymmetry > makes it really hard to clear up properly when using the asynchronous API, as > there is no way to "fail" data reads/updates when the client is closed. > I believe that the correct behaviour should be for all watchers to receive a > disconnection event when the client is closed. The watchers can then respond > as appropriate, and can differentiate between a "server disconnect" and a > "client disconnect" by checking the ZooKeeper#getState() method. > This would not be a breaking behaviour change as Watchers are already > required to handle disconnection events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper_branch34_solaris - Build # 1425 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1425/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 192375 lines...] [junit] 2017-01-09 13:56:43,123 [myid:] - INFO [main:ZooKeeperServer@497] - shutting down [junit] 2017-01-09 13:56:43,123 [myid:] - ERROR [main:ZooKeeperServer@472] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-09 13:56:43,123 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2017-01-09 13:56:43,123 [myid:] - INFO [main:PrepRequestProcessor@765] - Shutting down [junit] 2017-01-09 13:56:43,124 [myid:] - INFO [main:SyncRequestProcessor@208] - Shutting down [junit] 2017-01-09 13:56:43,124 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2017-01-09 13:56:43,124 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited! [junit] 2017-01-09 13:56:43,124 [myid:] - INFO [main:FinalRequestProcessor@402] - shutdown of request processor complete [junit] 2017-01-09 13:56:43,125 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2017-01-09 13:56:43,125 [myid:] - INFO [main:JMXEnv@147] - ensureOnly:[] [junit] 2017-01-09 13:56:43,126 [myid:] - INFO [main:ClientBase@445] - STARTING server [junit] 2017-01-09 13:56:43,126 [myid:] - INFO [main:ClientBase@366] - CREATING server instance 127.0.0.1:11221 [junit] 2017-01-09 13:56:43,126 [myid:] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2017-01-09 13:56:43,127 [myid:] - INFO [main:ClientBase@341] - STARTING server instance 127.0.0.1:11221 [junit] 2017-01-09 13:56:43,127 [myid:] - INFO [main:ZooKeeperServer@173] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test805454912456317188.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test805454912456317188.junit.dir/version-2 [junit] 2017-01-09 13:56:43,130 [myid:] - ERROR [main:ZooKeeperServer@472] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-09 13:56:43,130 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2017-01-09 13:56:43,130 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - Accepted socket connection from /127.0.0.1:37659 [junit] 2017-01-09 13:56:43,130 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:37659 [junit] 2017-01-09 13:56:43,131 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2017-01-09 13:56:43,132 [myid:] - INFO [Thread-5:NIOServerCnxn@1008] - Closed socket connection for client /127.0.0.1:37659 (no session established for client) [junit] 2017-01-09 13:56:43,132 [myid:] - INFO [main:JMXEnv@230] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2017-01-09 13:56:43,133 [myid:] - INFO [main:JMXEnv@247] - expect:InMemoryDataTree [junit] 2017-01-09 13:56:43,133 [myid:] - INFO [main:JMXEnv@251] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2017-01-09 13:56:43,133 [myid:] - INFO [main:JMXEnv@247] - expect:StandaloneServer_port [junit] 2017-01-09 13:56:43,133 [myid:] - INFO [main:JMXEnv@251] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2017-01-09 13:56:43,134 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 8947 [junit] 2017-01-09 13:56:43,134 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20 [junit] 2017-01-09 13:56:43,134 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota [junit] 2017-01-09 13:56:43,134 [myid:] - INFO [main:ClientBase@522] - tearDown starting [junit] 2017-01-09 13:56:43,212 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x15983844c5a closed [junit] 2017-01-09 13:56:43,212 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for session: 0x15983844c5a [junit] 2017-01-09 13:56:43,212 [myid:] - INFO [main:ClientBase@492] - STOPPING server [junit] 2017-01-09 13:56:43,213 [myid:] - INFO [main:ZooKeeperServer@497] - shutting down [junit] 2017-01-09 13:56:43,214 [myid:] - ERR
ZooKeeper_branch35_jdk8 - Build # 371 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/371/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 487512 lines...] [junit] 2017-01-09 12:22:02,432 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2017-01-09 12:22:02,432 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:24931 [junit] 2017-01-09 12:22:02,438 [myid:] - INFO [main:ZooKeeperServer@533] - shutting down [junit] 2017-01-09 12:22:02,440 [myid:] - ERROR [main:ZooKeeperServer@505] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-09 12:22:02,440 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2017-01-09 12:22:02,440 [myid:] - INFO [main:PrepRequestProcessor@974] - Shutting down [junit] 2017-01-09 12:22:02,440 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2017-01-09 12:22:02,440 [myid:] - INFO [ProcessThread(sid:0 cport:24931)::PrepRequestProcessor@154] - PrepRequestProcessor exited loop! [junit] 2017-01-09 12:22:02,440 [myid:] - INFO [main:FinalRequestProcessor@479] - shutdown of request processor complete [junit] 2017-01-09 12:22:02,440 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2017-01-09 12:22:02,441 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24931,name1=InMemoryDataTree] [junit] 2017-01-09 12:22:02,441 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port24931] [junit] 2017-01-09 12:22:02,441 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 24931 [junit] 2017-01-09 12:22:02,442 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2017-01-09 12:22:02,487 [myid:] - INFO [main:ClientBase@568] - fdcount after test is: 4833 at start it was 4829 [junit] 2017-01-09 12:22:02,488 [myid:] - INFO [main:ClientBase@570] - sleeping for 20 secs [junit] 2017-01-09 12:22:02,488 [myid:] - INFO [main:ZKTestCase$1@65] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2017-01-09 12:22:02,488 [myid:] - INFO [main:ZKTestCase$1@60] - FINISHED testWatcherAutoResetWithLocal [junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 581.567 sec, Thread: 6, Class: org.apache.zookeeper.test.NioNettySuiteTest [junit] 2017-01-09 12:22:02,642 [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] 2017-01-09 12:22:02,643 [myid:127.0.0.1:24811] - WARN [main-SendThread(127.0.0.1:24811):ClientCnxn$SendThread@1235] - Session 0x20316accd5f 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] 2017-01-09 12:22:02,817 [myid:127.0.0.1:24814] - INFO [main-SendThread(127.0.0.1:24814):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:24814. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-09 12:22:02,818 [myid:127.0.0.1:24814] - WARN [main-SendThread(127.0.0.1:24814):ClientCnxn$SendThread@1235] - Session 0x30316acce52 for server 127.0.0.1/127.0.0.1:24814, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-01-09 12:22:03,242 [myid:127.0.0.1:24808] - INFO [main-SendThread(127.0.0.1:24808):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:24808. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-09 12:22:03,243 [myid:127.0.0.1:24808] - WARN [main-SendThread(127.0.0.1:24808):ClientCnxn$SendThread@1235] - Session 0x10316accd5f for server 127.0.0.1/127.0.0.1:24808, unexpected error,
ZooKeeper-trunk-jdk8 - Build # 893 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/893/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 556657 lines...] [junit] 2017-01-09 12:08:30,323 [myid:] - WARN [NIOWorkerThread-22:NIOServerCnxn@369] - Exception causing close of session 0x0: ZooKeeperServer not running [junit] 2017-01-09 12:08:30,323 [myid:] - INFO [NIOWorkerThread-22:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:59257 (no session established for client) [junit] 2017-01-09 12:08:30,323 [myid:127.0.0.1:24765] - INFO [main-SendThread(127.0.0.1:24765):ClientCnxn$SendThread@1231] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect [junit] 2017-01-09 12:08:30,346 [myid:127.0.0.1:24753] - INFO [main-SendThread(127.0.0.1:24753):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:24753. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-09 12:08:30,347 [myid:127.0.0.1:24753] - INFO [main-SendThread(127.0.0.1:24753):ClientCnxn$SendThread@948] - Socket connection established, initiating session, client: /127.0.0.1:43626, server: 127.0.0.1/127.0.0.1:24753 [junit] 2017-01-09 12:08:30,347 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:/127.0.0.1:24753:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:43626 [junit] 2017-01-09 12:08:30,347 [myid:] - WARN [NIOWorkerThread-6:NIOServerCnxn@369] - Exception causing close of session 0x0: ZooKeeperServer not running [junit] 2017-01-09 12:08:30,347 [myid:] - INFO [NIOWorkerThread-6:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:43626 (no session established for client) [junit] 2017-01-09 12:08:30,347 [myid:127.0.0.1:24753] - INFO [main-SendThread(127.0.0.1:24753):ClientCnxn$SendThread@1231] - Unable to read additional data from server sessionid 0x10216cc30560001, likely server has closed socket, closing socket connection and attempting reconnect [junit] 2017-01-09 12:08:30,441 [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] 2017-01-09 12:08:30,441 [myid:127.0.0.1:24738] - WARN [main-SendThread(127.0.0.1:24738):ClientCnxn$SendThread@1235] - Session 0x20216cbfcc5 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] 2017-01-09 12:08:30,446 [myid:127.0.0.1:24756] - INFO [main-SendThread(127.0.0.1:24756):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:24756. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-01-09 12:08:30,446 [myid:127.0.0.1:24756] - INFO [main-SendThread(127.0.0.1:24756):ClientCnxn$SendThread@948] - Socket connection established, initiating session, client: /127.0.0.1:52428, server: 127.0.0.1/127.0.0.1:24756 [junit] 2017-01-09 12:08:30,446 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:/127.0.0.1:24756:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:52428 [junit] 2017-01-09 12:08:30,447 [myid:] - WARN [NIOWorkerThread-28:NIOServerCnxn@369] - Exception causing close of session 0x0: ZooKeeperServer not running [junit] 2017-01-09 12:08:30,447 [myid:] - INFO [NIOWorkerThread-28:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:52428 (no session established for client) [junit] 2017-01-09 12:08:30,447 [myid:127.0.0.1:24756] - INFO [main-SendThread(127.0.0.1:24756):ClientCnxn$SendThread@1231] - Unable to read additional data from server sessionid 0x20216cc2fc8, likely server has closed socket, closing socket connection and attempting reconnect [junit] 2017-01-09 12:08:30,502 [myid:] - WARN [QuorumPeer[myid=2](plain=/127.0.0.1:24756)(secure=disabled):Learner@273] - Unexpected exception, tries=3, remaining init limit=2999, connecting to /127.0.0.1:24760 [junit] java.net.ConnectException: Connection refused [junit] at java.net.PlainSocketImpl.socketConnect(Native Method) [junit] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [junit] at java.net.AbstractPlainSocketImpl.connectTo
ZooKeeper_branch35_openjdk7 - Build # 366 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/366/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H16 (ubuntu) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress
> git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/branch-3.5^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/branch-3.5^{commit} # timeout=10
Checking out Revision 3cdaeedf8b59da50421c5b6bba1d3f72dcfdd661
(refs/remotes/origin/branch-3.5)
> git config core.sparsecheckout # timeout=10
> git checkout -f 3cdaeedf8b59da50421c5b6bba1d3f72dcfdd661
> git rev-list 3cdaeedf8b59da50421c5b6bba1d3f72dcfdd661 # timeout=10
No emails were triggered.
[ZooKeeper_branch35_openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml
-Djavac.target=1.7 clean test-core-java
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
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.
ZooKeeper-trunk-solaris - Build # 1458 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1458/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 487055 lines...] [junit] 2017-01-09 09:03:02,318 [myid:] - INFO [main:ClientBase@386] - CREATING server instance 127.0.0.1:11222 [junit] 2017-01-09 09:03:02,318 [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] 2017-01-09 09:03:02,319 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2017-01-09 09:03:02,319 [myid:] - INFO [main:ClientBase@361] - STARTING server instance 127.0.0.1:11222 [junit] 2017-01-09 09:03:02,320 [myid:] - INFO [main:ZooKeeperServer@894] - minSessionTimeout set to 6000 [junit] 2017-01-09 09:03:02,320 [myid:] - INFO [main:ZooKeeperServer@903] - maxSessionTimeout set to 6 [junit] 2017-01-09 09:03:02,320 [myid:] - INFO [main:ZooKeeperServer@160] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test6200600793223341620.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test6200600793223341620.junit.dir/version-2 [junit] 2017-01-09 09:03:02,321 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test6200600793223341620.junit.dir/version-2/snapshot.b [junit] 2017-01-09 09:03:02,322 [myid:] - INFO [main:FileTxnSnapLog@320] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test6200600793223341620.junit.dir/version-2/snapshot.b [junit] 2017-01-09 09:03:02,324 [myid:] - ERROR [main:ZooKeeperServer@506] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-01-09 09:03:02,324 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222 [junit] 2017-01-09 09:03:02,324 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:62154 [junit] 2017-01-09 09:03:02,325 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:62154 [junit] 2017-01-09 09:03:02,325 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2017-01-09 09:03:02,326 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@614] - Closed socket connection for client /127.0.0.1:62154 (no session established for client) [junit] 2017-01-09 09:03:02,326 [myid:] - INFO [main:JMXEnv@228] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2017-01-09 09:03:02,327 [myid:] - INFO [main:JMXEnv@245] - expect:InMemoryDataTree [junit] 2017-01-09 09:03:02,327 [myid:] - INFO [main:JMXEnv@249] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2017-01-09 09:03:02,327 [myid:] - INFO [main:JMXEnv@245] - expect:StandaloneServer_port [junit] 2017-01-09 09:03:02,328 [myid:] - INFO [main:JMXEnv@249] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2017-01-09 09:03:02,328 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17912 [junit] 2017-01-09 09:03:02,328 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2017-01-09 09:03:02,328 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2017-01-09 09:03:02,328 [myid:] - INFO [main:ClientBase@543] - tearDown starting [junit] 2017-01-09 09:03:02,402 [myid:] - INFO [main:ZooKeeper@1313] - Session: 0x125ff70f102 closed [junit] 2017-01-09 09:03:02,402 [myid:] - INFO [main:ClientBase@513] - STOPPING server [junit] 2017-01-09 09:03:02,402 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x125ff70f102 [junit] 2017-01-09 09:03:02,402 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2017-01-09 09:03:02,402 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2017-01-09 09:03:02,402 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread
