ZooKeeper_branch34_solaris - Build # 694 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/694/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 153324 lines...] [junit] 2013-10-30 08:02:22,665 [myid:] - INFO [Thread-4:NIOServerCnxn@997] - Closed socket connection for client /127.0.0.1:60564 (no session established for client) [junit] 2013-10-30 08:02:22,666 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-30 08:02:22,667 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-30 08:02:22,667 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-30 08:02:22,668 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-30 08:02:22,668 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-30 08:02:22,668 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-30 08:02:22,669 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2013-10-30 08:02:22,669 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2013-10-30 08:02:22,669 [myid:] - INFO [main:PrepRequestProcessor@761] - Shutting down [junit] 2013-10-30 08:02:22,670 [myid:] - INFO [main:SyncRequestProcessor@209] - Shutting down [junit] 2013-10-30 08:02:22,670 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2013-10-30 08:02:22,670 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited! [junit] 2013-10-30 08:02:22,670 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2013-10-30 08:02:22,671 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 08:02:22,671 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-30 08:02:22,673 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-30 08:02:22,673 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test7071971172557577381.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test7071971172557577381.junit.dir/version-2 [junit] 2013-10-30 08:02:22,674 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-30 08:02:22,676 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 08:02:22,677 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:60566 [junit] 2013-10-30 08:02:22,677 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@817] - Processing stat command from /127.0.0.1:60566 [junit] 2013-10-30 08:02:22,678 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@653] - Stat command output [junit] 2013-10-30 08:02:22,679 [myid:] - INFO [Thread-5:NIOServerCnxn@997] - Closed socket connection for client /127.0.0.1:60566 (no session established for client) [junit] 2013-10-30 08:02:22,679 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-30 08:02:22,681 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-30 08:02:22,681 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-30 08:02:22,681 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-30 08:02:22,681 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-30 08:02:22,682 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-30 08:02:22,682 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-30 08:02:23,548 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x14208627c0e closed [junit] 2013-10-30 08:02:23,548 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@509] - EventThread shut down [junit] 2013-10-30 08:02:23,549 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-30 08:02:23,551 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2013-10-30 08:02:23,551
ZooKeeper-trunk-solaris - Build # 716 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/716/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 221476 lines...] [junit] 2013-10-30 09:03:17,210 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2013-10-30 09:03:17,211 [myid:] - INFO [main:ZooKeeperServer@428] - shutting down [junit] 2013-10-30 09:03:17,211 [myid:] - INFO [main:SessionTrackerImpl@183] - Shutting down [junit] 2013-10-30 09:03:17,211 [myid:] - INFO [main:PrepRequestProcessor@972] - Shutting down [junit] 2013-10-30 09:03:17,211 [myid:] - INFO [main:SyncRequestProcessor@190] - Shutting down [junit] 2013-10-30 09:03:17,211 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-10-30 09:03:17,212 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2013-10-30 09:03:17,212 [myid:] - INFO [main:FinalRequestProcessor@442] - shutdown of request processor complete [junit] 2013-10-30 09:03:17,213 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 09:03:17,213 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-30 09:03:17,214 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-30 09:03:17,214 [myid:] - INFO [main:ZooKeeperServer@149] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4450879718972686136.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4450879718972686136.junit.dir/version-2 [junit] 2013-10-30 09:03:17,215 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 kB direct buffers. [junit] 2013-10-30 09:03:17,215 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-30 09:03:17,216 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4450879718972686136.junit.dir/version-2/snapshot.b [junit] 2013-10-30 09:03:17,219 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4450879718972686136.junit.dir/version-2/snapshot.b [junit] 2013-10-30 09:03:17,221 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 09:03:17,221 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:39497 [junit] 2013-10-30 09:03:17,222 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@828] - Processing stat command from /127.0.0.1:39497 [junit] 2013-10-30 09:03:17,222 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@677] - Stat command output [junit] 2013-10-30 09:03:17,223 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@999] - Closed socket connection for client /127.0.0.1:39497 (no session established for client) [junit] 2013-10-30 09:03:17,223 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-30 09:03:17,224 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-30 09:03:17,225 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-30 09:03:17,225 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-30 09:03:17,225 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-30 09:03:17,225 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-30 09:03:17,225 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-30 09:03:17,290 [myid:] - INFO [main:ZooKeeper@777] - Session: 0x142089a3fee closed [junit] 2013-10-30 09:03:17,290 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down [junit] 2013-10-30 09:03:17,291 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-30 09:03:17,292 [myid:] - INFO
ZooKeeper-3.4-WinVS2008_java - Build # 338 - Still Failing
See https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java/338/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 192989 lines...] [junit] 2013-10-30 10:10:22,145 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2013-10-30 10:10:22,146 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 10:10:23,134 [myid:] - WARN [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1095] - Session 0x14208d7a51b for server null, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused: no further information [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1074) [junit] 2013-10-30 10:10:23,145 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-30 10:10:23,152 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-30 10:10:23,152 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir f:\hudson\hudson-slave\workspace\ZooKeeper-3.4-WinVS2008_java\branch-3.4\build\test\tmp\test2839215363646038113.junit.dir\version-2 snapdir f:\hudson\hudson-slave\workspace\ZooKeeper-3.4-WinVS2008_java\branch-3.4\build\test\tmp\test2839215363646038113.junit.dir\version-2 [junit] 2013-10-30 10:10:23,252 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-30 10:10:23,256 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 10:10:23,257 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:60447 [junit] 2013-10-30 10:10:23,257 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@817] - Processing stat command from /127.0.0.1:60447 [junit] 2013-10-30 10:10:23,352 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@653] - Stat command output [junit] 2013-10-30 10:10:23,353 [myid:] - INFO [Thread-5:NIOServerCnxn@997] - Closed socket connection for client /127.0.0.1:60447 (no session established for client) [junit] 2013-10-30 10:10:23,353 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-30 10:10:23,355 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-30 10:10:23,355 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-30 10:10:23,454 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-30 10:10:23,454 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-30 10:10:23,454 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-30 10:10:23,454 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-30 10:10:24,000 [myid:] - INFO [SessionTracker:SessionTrackerImpl@162] - SessionTrackerImpl exited loop! [junit] 2013-10-30 10:10:24,359 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@968] - Opening socket connection to server 127.0.0.1/127.0.0.1:11221. Will not attempt to authenticate using SASL (java.lang.SecurityException: Unable to locate a login configuration) [junit] 2013-10-30 10:10:24,359 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@849] - Socket connection established to 127.0.0.1/127.0.0.1:11221, initiating session [junit] 2013-10-30 10:10:24,360 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:60471 [junit] 2013-10-30 10:10:24,459 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:ZooKeeperServer@861] - Client attempting to renew session 0x14208d7a51b at /127.0.0.1:60471 [junit] 2013-10-30 10:10:24,460 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:ZooKeeperServer@617] - Established session 0x14208d7a51b with negotiated timeout 3 for client /127.0.0.1:60471 [junit] 2013-10-30 10:10:24,460 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1228] - Session establishment complete on server 127.0.0.1/127.0.0.1:11221, sessionid = 0x14208d7a51b,
ZooKeeper_branch34_openjdk7 - Build # 384 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/384/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 211785 lines...] [junit] 2013-10-30 10:20:41,671 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-30 10:20:41,672 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-30 10:20:41,672 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-30 10:20:41,672 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-30 10:20:41,672 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-30 10:20:41,673 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@224] - NIOServerCnxn factory exited run method [junit] 2013-10-30 10:20:41,673 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2013-10-30 10:20:41,673 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2013-10-30 10:20:41,673 [myid:] - INFO [main:PrepRequestProcessor@761] - Shutting down [junit] 2013-10-30 10:20:41,673 [myid:] - INFO [main:SyncRequestProcessor@209] - Shutting down [junit] 2013-10-30 10:20:41,673 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2013-10-30 10:20:41,674 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited! [junit] 2013-10-30 10:20:41,674 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2013-10-30 10:20:41,675 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 10:20:41,675 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-30 10:20:41,676 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-30 10:20:41,677 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test6690047780486757159.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test6690047780486757159.junit.dir/version-2 [junit] 2013-10-30 10:20:41,677 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-30 10:20:41,681 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 10:20:41,681 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:51376 [junit] 2013-10-30 10:20:41,681 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@817] - Processing stat command from /127.0.0.1:51376 [junit] 2013-10-30 10:20:41,682 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@653] - Stat command output [junit] 2013-10-30 10:20:41,682 [myid:] - INFO [Thread-4:NIOServerCnxn@997] - Closed socket connection for client /127.0.0.1:51376 (no session established for client) [junit] 2013-10-30 10:20:41,682 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-30 10:20:41,684 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-30 10:20:41,684 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-30 10:20:41,684 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-30 10:20:41,685 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-30 10:20:41,685 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-30 10:20:41,685 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-30 10:20:41,758 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x14208e121ca closed [junit] 2013-10-30 10:20:41,758 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@509] - EventThread shut down [junit] 2013-10-30 10:20:41,758 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-30 10:20:41,759 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@224] - NIOServerCnxn factory exited run method [junit] 2013-10-30 10:20:41,759 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2013-10-30 10:20:41,759
ZooKeeper-trunk-WinVS2008_java - Build # 586 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008_java/586/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 296254 lines...] [junit] 2013-10-30 10:32:30,534 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down [junit] 2013-10-30 10:32:30,534 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2013-10-30 10:32:30,534 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2013-10-30 10:32:30,711 [myid:] - INFO [main:ZooKeeperServer@428] - shutting down [junit] 2013-10-30 10:32:30,711 [myid:] - INFO [main:SessionTrackerImpl@183] - Shutting down [junit] 2013-10-30 10:32:30,711 [myid:] - INFO [main:PrepRequestProcessor@972] - Shutting down [junit] 2013-10-30 10:32:30,711 [myid:] - INFO [main:SyncRequestProcessor@190] - Shutting down [junit] 2013-10-30 10:32:30,711 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-10-30 10:32:30,712 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2013-10-30 10:32:30,812 [myid:] - INFO [main:FinalRequestProcessor@442] - shutdown of request processor complete [junit] 2013-10-30 10:32:30,812 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 10:32:31,806 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-30 10:32:31,810 [myid:] - INFO [main:ZKTestCase$1@66] - FAILED testQuota [junit] junit.framework.AssertionFailedError: expected:0 but was:1 [junit] at junit.framework.Assert.fail(Assert.java:50) [junit] at junit.framework.Assert.failNotEquals(Assert.java:287) [junit] at junit.framework.Assert.assertEquals(Assert.java:67) [junit] at junit.framework.Assert.assertEquals(Assert.java:199) [junit] at junit.framework.Assert.assertEquals(Assert.java:205) [junit] at org.apache.zookeeper.test.JMXEnv.ensureOnly(JMXEnv.java:138) [junit] at org.apache.zookeeper.test.ClientBase.startServer(ClientBase.java:417) [junit] at org.apache.zookeeper.test.ZooKeeperQuotaTest.testQuota(ZooKeeperQuotaTest.java:72) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) [junit] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) [junit] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) [junit] at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) [junit] at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52) [junit] at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) [junit] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) [junit] at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:52) [junit] at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) [junit] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:69) [junit] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:48) [junit] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) [junit] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) [junit] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) [junit] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) [junit] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) [junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:292) [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906) [junit] 2013-10-30 10:32:31,818 [myid:] - INFO [main:ZKTestCase$1@56] - FINISHED testQuota
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809040#comment-13809040 ] Flavio Junqueira commented on ZOOKEEPER-1805: - I forgot to mention that it would be nice if [~abranzyck] and [~rgs] could comment and test this fix. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Germán Blanco updated ZOOKEEPER-1805: - Attachment: ZOOKEEPER-1805.patch Sorry but, according to my tests, your changes do not work. When doing a rolling upgrade of zookeeper 3.4.5 to the trunk with this patch applied, the third server fails to join the quorum after restart. Since I had the setup ready, I tested this other patch and it seems to work. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809193#comment-13809193 ] Flavio Junqueira commented on ZOOKEEPER-1805: - I don't understand why it needs to be epoch - 1 for the rolling upgrade to work. I also don't understand why my changes didn't work in your setting (not that I have had time to test exhaustively). Could you post the logs please? Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809271#comment-13809271 ] Flavio Junqueira commented on ZOOKEEPER-1805: - I think I get it now, in ZOOKEEPER-1732 we have made two fields don't care and we update the epoch value. The epoch value is causing the comparison to fail, but I think that the don't care values also have to be updated in the way I propose, otherwise the comparison will fail too, no? newEpoch - 1 sounds like a hack to me, not a principled solution. I need to think a bit more about this one. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-429) Provide separate read and write threads in the bookkeeper server
[
https://issues.apache.org/jira/browse/BOOKKEEPER-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809305#comment-13809305
]
Hadoop QA commented on BOOKKEEPER-429:
--
Testing JIRA BOOKKEEPER-429
Patch
[0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch|https://issues.apache.org/jira/secure/attachment/12611103/0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch]
downloaded at Wed Oct 30 16:12:19 UTC 2013
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
120
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:red}-1 TESTS{color}
.Tests run: 886
.Tests failed: 0
.Tests errors: 3
.The patch failed the following testcases:
.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/526/
Provide separate read and write threads in the bookkeeper server
Key: BOOKKEEPER-429
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-429
Project: Bookkeeper
Issue Type: Improvement
Components: bookkeeper-server
Affects Versions: 4.2.0
Reporter: Aniruddha
Assignee: Aniruddha
Fix For: 4.3.0
Attachments:
0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch,
BK-429.patch, BOOKKEEPER-429.diff, BOOKKEEPER-429.diff
The current bookkeeper server is single threaded. The same thread handles
reads and writes. When reads are slow (possibly because of excessive seeks),
add entry operations suffer in terms of latencies. Providing separate read
and write threads helps in reducing add entry latencies and increasing
throughput even when we're facing slow reads. Having a single read thread
also results in low disk utilization because seeks can't be ordered
efficiently by the OS. Multiple read threads would help in improving the read
throughput.
Discussion on this can be found at
http://mail-archives.apache.org/mod_mbox/zookeeper-bookkeeper-dev/201209.mbox/%3ccaolhydqpzn-v10zynfwud_h0qzrxtmjgttx7a9eofohyyty...@mail.gmail.com%3e
Reviewboard : https://reviews.apache.org/r/7560/
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated ZOOKEEPER-1805: Attachment: ZOOKEEPER-1805.patch What about this, [~abranzyck]? Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809381#comment-13809381 ] Hadoop QA commented on ZOOKEEPER-1805: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/1260/ZOOKEEPER-1805.patch against trunk revision 1535491. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +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 1.3.9) 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/1728//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1728//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1728//console This message is automatically generated. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
Failed: ZOOKEEPER-1805 PreCommit Build #1728
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1728/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 253915 lines...] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/1260/ZOOKEEPER-1805.patch [exec] against trunk revision 1535491. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [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 1.3.9) 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/1728//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1728//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1728//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] dcbfabd1f08190fdf8836912b2cf60a1f3747048 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1623: exec returned: 1 Total time: 33 minutes 0 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1805 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809386#comment-13809386 ] Raul Gutierrez Segales commented on ZOOKEEPER-1805: --- Testing this now - thanks for the patch [~fpj]. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809399#comment-13809399
]
Sijie Guo commented on BOOKKEEPER-700:
--
{quote}
IMHO, one way to address this would be to create a common 'BookieThread' that
all the threads must extend and every thread can define following properties:
{quote}
there is already a BookieThread doing this. you don't need to create a new
class. But I don't think GarbageCollectorThread is critical enough to do this,
as the garbage collector thread quits doesn't affect anything.
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch, 0002-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-628) Improve bookie registration interface
[ https://issues.apache.org/jira/browse/BOOKKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809407#comment-13809407 ] Sijie Guo commented on BOOKKEEPER-628: -- I don't think it is a good idea to refactor things that would be changed in future. since you don't actually know whether the refactor meets the changes or not. if this is really really need to be in, I would suggest doing the metadata related part (not session expire part), like Cookies. And we could iterate the session part later. Improve bookie registration interface - Key: BOOKKEEPER-628 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-628 Project: Bookkeeper Issue Type: Improvement Components: bookkeeper-client, bookkeeper-server Reporter: Rakesh R Assignee: Rakesh R Fix For: 4.3.0 Attachments: BOOKKEEPER-628-interface-version-1.patch, BOOKKEEPER-628-interface-version-2.patch, BOOKKEEPER-628-interface-version.patch The idea is to improve/generalize the bookie registration process -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809419#comment-13809419 ] Raul Gutierrez Segales commented on ZOOKEEPER-1805: --- [~fpj]: did a quick test and followers joined nicely - thanks! Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809461#comment-13809461 ] Germán Blanco commented on ZOOKEEPER-1805: -- The reason why the changes in Vote are not required is because all the Votes inserted in outofelection have the same values for zxid and election epoch. So the comparison is already based only in the other fields of Vote. The value newEpoch - 1 works because we want to get back to the last accepted epoch of the leader, and the leader is sending the last accepted epoch plus one. The newEpoch that is sent from the Leader to all learners is calculated in getEpochToPropose in Leader.java. My interpretation of that method is that the new epoch will always be lastAcceptedEpoch plus one. There are at least these other alternatives, but they look worse: - ignoring also peerEpoch in the comparison. Which will have the risk of taking into account left-over votes of ensembles established before the current one. - setting peerEpoch to any other value. Has the same problem that we are trying to fix. - changing the protocol in order to send lastAcceptedEpoch (and maybe zxid and election epoch, since the protocol is changed anyway) instead of the new epoch. I will provide the logs tomorrow. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809483#comment-13809483 ] Germán Blanco commented on ZOOKEEPER-1805: -- I sent that last comment without refreshing the page. It seems the logs are not needed any longer, since the last patch fixes the problem. My interpretation of your last patch is that you are not taking peerEpoch in the comparison. For outofelection all zxids equal Vote.DONTCARE, so the condition results in not using peerEpoch. That is the first option in my previous comment. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
ZooKeeper-trunk-openjdk7 - Build # 307 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/307/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 245186 lines...] [junit] 2013-10-30 23:43:02,081 [myid:] - INFO [main:ZooKeeperServer@428] - shutting down [junit] 2013-10-30 23:43:02,081 [myid:] - INFO [main:SessionTrackerImpl@183] - Shutting down [junit] 2013-10-30 23:43:02,081 [myid:] - INFO [main:PrepRequestProcessor@972] - Shutting down [junit] 2013-10-30 23:43:02,081 [myid:] - INFO [main:SyncRequestProcessor@190] - Shutting down [junit] 2013-10-30 23:43:02,081 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-10-30 23:43:02,082 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2013-10-30 23:43:02,082 [myid:] - INFO [main:FinalRequestProcessor@442] - shutdown of request processor complete [junit] 2013-10-30 23:43:02,083 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 23:43:02,083 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-30 23:43:02,085 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-30 23:43:02,085 [myid:] - INFO [main:ZooKeeperServer@149] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test2844466308736478523.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test2844466308736478523.junit.dir/version-2 [junit] 2013-10-30 23:43:02,085 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 kB direct buffers. [junit] 2013-10-30 23:43:02,086 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-30 23:43:02,087 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test2844466308736478523.junit.dir/version-2/snapshot.b [junit] 2013-10-30 23:43:02,090 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test2844466308736478523.junit.dir/version-2/snapshot.b [junit] 2013-10-30 23:43:02,093 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-30 23:43:02,093 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:32933 [junit] 2013-10-30 23:43:02,094 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@828] - Processing stat command from /127.0.0.1:32933 [junit] 2013-10-30 23:43:02,095 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@677] - Stat command output [junit] 2013-10-30 23:43:02,095 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@999] - Closed socket connection for client /127.0.0.1:32933 (no session established for client) [junit] 2013-10-30 23:43:02,095 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-30 23:43:02,098 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-30 23:43:02,098 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-30 23:43:02,098 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-30 23:43:02,098 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-30 23:43:02,099 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-30 23:43:02,099 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-30 23:43:02,150 [myid:] - INFO [main:ZooKeeper@777] - Session: 0x1420bbfb12b closed [junit] 2013-10-30 23:43:02,150 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down [junit] 2013-10-30 23:43:02,150 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-30 23:43:02,150 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2013-10-30 23:43:02,151 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2013-10-30 23:43:02,151 [myid:] - INFO
[jira] [Updated] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated ZOOKEEPER-1805: Attachment: ZOOKEEPER-1805.patch Added unit tests. Thanks for having a look, guys. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1805) Don't care value in ZooKeeper election breaks rolling upgrades
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809947#comment-13809947 ] Hadoop QA commented on ZOOKEEPER-1805: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12611251/ZOOKEEPER-1805.patch against trunk revision 1535491. +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 1.3.9) 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/1729//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1729//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1729//console This message is automatically generated. Don't care value in ZooKeeper election breaks rolling upgrades Key: ZOOKEEPER-1805 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Project: ZooKeeper Issue Type: Bug Reporter: Flavio Junqueira Assignee: Flavio Junqueira Priority: Blocker Attachments: ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch, ZOOKEEPER-1805.patch This is an issue that has been originally reported in ZOOKEEPER-1732. -- This message was sent by Atlassian JIRA (v6.1#6144)
Success: ZOOKEEPER-1805 PreCommit Build #1729
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1805 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1729/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 28 lines...] [exec] BUILD SUCCESSFUL [exec] Total time: 0 seconds [exec] [exec] [exec] [exec] [exec] +1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12611251/ZOOKEEPER-1805.patch [exec] against trunk revision 1535491. [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 1.3.9) 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/1729//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1729//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1729//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] caaeeb146a6a0ca97d4182aacb5028f144ac8823 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 33 minutes 11 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1805 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Created] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
Rakesh R created BOOKKEEPER-700:
---
Summary: GarbageCollectorThread exsiting with
ArrayIndexOutOfBoundsException
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated BOOKKEEPER-700:
Attachment: 0001-BOOKKEEPER-700.patch
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808903#comment-13808903
]
Hadoop QA commented on BOOKKEEPER-700:
--
Testing JIRA BOOKKEEPER-700
Patch
[0001-BOOKKEEPER-700.patch|https://issues.apache.org/jira/secure/attachment/12611014/0001-BOOKKEEPER-700.patch]
downloaded at Wed Oct 30 09:22:00 UTC 2013
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
120
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:green}+1 TESTS{color}
.Tests run: 882
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/521/
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808901#comment-13808901
]
Rakesh R commented on BOOKKEEPER-700:
-
Here to fix this, I just made simple size check. Could you please review the
changes. Thanks.
While seeing this issue, I just noticed one case. If a thread is a critical
thread(for ex: GarbageCollectorThread) and assume any unexpected exceptions
occured, it may exit without any logs and makes debugging difficult.
*Proposal:*
If we have ThreadGroup exception handler to all the threads and will define
setUncaughtExceptionHandler to caught all exceptions thrown by Thread run
methods.
IMHO, one way to address this would be to create a common 'BookieThread' that
all the threads must extend and every thread can define following properties:
# threadName,
# isUnhandledExceptionFatal - if yes log as fatal error and call
System.exit(errcode), otw just log with priority level error and continue
running server.
Shall I raise a separate JIRA for this thought and work for the same. Whats
your opinion?
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-699) Codahale metrics implementation of stats API
[ https://issues.apache.org/jira/browse/BOOKKEEPER-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808907#comment-13808907 ] Ivan Kelly commented on BOOKKEEPER-699: --- stupid fingers. New patch attached. Codahale metrics implementation of stats API Key: BOOKKEEPER-699 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-699 Project: Bookkeeper Issue Type: Improvement Reporter: Ivan Kelly Assignee: Ivan Kelly Fix For: 4.3.0 Attachments: 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch, 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch As title says, add codahale metrics implementation of stats collection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (BOOKKEEPER-699) Codahale metrics implementation of stats API
[ https://issues.apache.org/jira/browse/BOOKKEEPER-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-699: -- Attachment: 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch Codahale metrics implementation of stats API Key: BOOKKEEPER-699 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-699 Project: Bookkeeper Issue Type: Improvement Reporter: Ivan Kelly Assignee: Ivan Kelly Fix For: 4.3.0 Attachments: 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch, 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch As title says, add codahale metrics implementation of stats collection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-699) Codahale metrics implementation of stats API
[
https://issues.apache.org/jira/browse/BOOKKEEPER-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808933#comment-13808933
]
Hadoop QA commented on BOOKKEEPER-699:
--
Testing JIRA BOOKKEEPER-699
Patch
[0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch|https://issues.apache.org/jira/secure/attachment/12611020/0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch]
downloaded at Wed Oct 30 10:01:59 UTC 2013
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
120
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:green}+1 TESTS{color}
.Tests run: 882
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/522/
Codahale metrics implementation of stats API
Key: BOOKKEEPER-699
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-699
Project: Bookkeeper
Issue Type: Improvement
Reporter: Ivan Kelly
Assignee: Ivan Kelly
Fix For: 4.3.0
Attachments:
0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch,
0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch
As title says, add codahale metrics implementation of stats collection.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (BOOKKEEPER-696) stats collection on bookkeeper client
[ https://issues.apache.org/jira/browse/BOOKKEEPER-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-696: -- Attachment: 0002-BOOKKEEPER-696-stats-collection-on-bookkeeper-client.patch stats collection on bookkeeper client - Key: BOOKKEEPER-696 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-696 Project: Bookkeeper Issue Type: Sub-task Components: bookkeeper-client Reporter: Sijie Guo Assignee: Aniruddha Fix For: 4.3.0 Attachments: 0001-client-stats-for-bookkeeper.patch, 0002-BOOKKEEPER-696-stats-collection-on-bookkeeper-client.patch Stats for bookkeeper client. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (BOOKKEEPER-699) Codahale metrics implementation of stats API
[ https://issues.apache.org/jira/browse/BOOKKEEPER-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-699: -- Attachment: 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch Reporters weren't starting. New patch fixes this. Codahale metrics implementation of stats API Key: BOOKKEEPER-699 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-699 Project: Bookkeeper Issue Type: Improvement Reporter: Ivan Kelly Assignee: Ivan Kelly Fix For: 4.3.0 Attachments: 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch, 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch, 0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch As title says, add codahale metrics implementation of stats collection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-696) stats collection on bookkeeper client
[ https://issues.apache.org/jira/browse/BOOKKEEPER-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808978#comment-13808978 ] Ivan Kelly commented on BOOKKEEPER-696: --- Added patch using constant strings rather than enums. BookKeeperClientStats is quite similar to BookkeeperClientStatsLogger, but it's in the client package, to avoid having to import it every time. Since everything uses the StatsLogger interface now, BookkeeperStatsLogger, ClientStatsProvider PCBookieClientStatsLogger are not needed. Also, this patch has the builder for BookKeeper. stats collection on bookkeeper client - Key: BOOKKEEPER-696 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-696 Project: Bookkeeper Issue Type: Sub-task Components: bookkeeper-client Reporter: Sijie Guo Assignee: Aniruddha Fix For: 4.3.0 Attachments: 0001-client-stats-for-bookkeeper.patch, 0002-BOOKKEEPER-696-stats-collection-on-bookkeeper-client.patch Stats for bookkeeper client. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808984#comment-13808984
]
Ivan Kelly commented on BOOKKEEPER-700:
---
Hmm, I guess this happens when nothing has been deleted. Good catch. Could you
add a test for this also. I checked 4.2.0 and this doesn't exist there.
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-628) Improve bookie registration interface
[ https://issues.apache.org/jira/browse/BOOKKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808989#comment-13808989 ] Ivan Kelly commented on BOOKKEEPER-628: --- which smaller chunk though? Improve bookie registration interface - Key: BOOKKEEPER-628 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-628 Project: Bookkeeper Issue Type: Improvement Components: bookkeeper-client, bookkeeper-server Reporter: Rakesh R Assignee: Rakesh R Fix For: 4.3.0 Attachments: BOOKKEEPER-628-interface-version-1.patch, BOOKKEEPER-628-interface-version-2.patch, BOOKKEEPER-628-interface-version.patch The idea is to improve/generalize the bookie registration process -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-628) Improve bookie registration interface
[ https://issues.apache.org/jira/browse/BOOKKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809003#comment-13809003 ] Rakesh R commented on BOOKKEEPER-628: - bq.which smaller chunk though? I meant, RegistrationManager#ManagerListener part, which will be used to listen for zk connection events. Improve bookie registration interface - Key: BOOKKEEPER-628 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-628 Project: Bookkeeper Issue Type: Improvement Components: bookkeeper-client, bookkeeper-server Reporter: Rakesh R Assignee: Rakesh R Fix For: 4.3.0 Attachments: BOOKKEEPER-628-interface-version-1.patch, BOOKKEEPER-628-interface-version-2.patch, BOOKKEEPER-628-interface-version.patch The idea is to improve/generalize the bookie registration process -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-628) Improve bookie registration interface
[ https://issues.apache.org/jira/browse/BOOKKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809004#comment-13809004 ] Ivan Kelly commented on BOOKKEEPER-628: --- Hmm, actually looking at this again, perhaps it could go in before BOOKKEEPER-537, if the previous comments are addressed. Then BOOKKEEPER-537 could build on top. Improve bookie registration interface - Key: BOOKKEEPER-628 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-628 Project: Bookkeeper Issue Type: Improvement Components: bookkeeper-client, bookkeeper-server Reporter: Rakesh R Assignee: Rakesh R Fix For: 4.3.0 Attachments: BOOKKEEPER-628-interface-version-1.patch, BOOKKEEPER-628-interface-version-2.patch, BOOKKEEPER-628-interface-version.patch The idea is to improve/generalize the bookie registration process -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-696) stats collection on bookkeeper client
[
https://issues.apache.org/jira/browse/BOOKKEEPER-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809007#comment-13809007
]
Hadoop QA commented on BOOKKEEPER-696:
--
Testing JIRA BOOKKEEPER-696
Patch
[0002-BOOKKEEPER-696-stats-collection-on-bookkeeper-client.patch|https://issues.apache.org/jira/secure/attachment/12611030/0002-BOOKKEEPER-696-stats-collection-on-bookkeeper-client.patch]
downloaded at Wed Oct 30 11:21:59 UTC 2013
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
120
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:green}+1 TESTS{color}
.Tests run: 882
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/523/
stats collection on bookkeeper client
-
Key: BOOKKEEPER-696
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-696
Project: Bookkeeper
Issue Type: Sub-task
Components: bookkeeper-client
Reporter: Sijie Guo
Assignee: Aniruddha
Fix For: 4.3.0
Attachments: 0001-client-stats-for-bookkeeper.patch,
0002-BOOKKEEPER-696-stats-collection-on-bookkeeper-client.patch
Stats for bookkeeper client.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-699) Codahale metrics implementation of stats API
[
https://issues.apache.org/jira/browse/BOOKKEEPER-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809021#comment-13809021
]
Hadoop QA commented on BOOKKEEPER-699:
--
Testing JIRA BOOKKEEPER-699
Patch
[0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch|https://issues.apache.org/jira/secure/attachment/12611029/0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch]
downloaded at Wed Oct 30 11:50:00 UTC 2013
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
120
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:green}+1 TESTS{color}
.Tests run: 882
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/524/
Codahale metrics implementation of stats API
Key: BOOKKEEPER-699
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-699
Project: Bookkeeper
Issue Type: Improvement
Reporter: Ivan Kelly
Assignee: Ivan Kelly
Fix For: 4.3.0
Attachments:
0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch,
0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch,
0001-BOOKKEEPER-699-Codahale-metrics-implementation-of-st.patch
As title says, add codahale metrics implementation of stats collection.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated BOOKKEEPER-700:
Attachment: 0002-BOOKKEEPER-700.patch
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch, 0002-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809157#comment-13809157
]
Rakesh R commented on BOOKKEEPER-700:
-
Thanks Ivan for the reviews. Attached latest patch with tests, please have a
look at it.
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch, 0002-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809168#comment-13809168
]
Ivan Kelly commented on BOOKKEEPER-700:
---
new patch looks good. running tests now.
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch, 0002-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809196#comment-13809196
]
Hadoop QA commented on BOOKKEEPER-700:
--
Testing JIRA BOOKKEEPER-700
Patch
[0002-BOOKKEEPER-700.patch|https://issues.apache.org/jira/secure/attachment/12611073/0002-BOOKKEEPER-700.patch]
downloaded at Wed Oct 30 14:40:59 UTC 2013
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
120
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:green}+1 TESTS{color}
.Tests run: 883
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/525/
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch, 0002-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Jenkins build is back to normal : bookkeeper-trunk #424
See https://builds.apache.org/job/bookkeeper-trunk/424/changes
[jira] [Commented] (BOOKKEEPER-700) GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/BOOKKEEPER-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809263#comment-13809263
]
Hudson commented on BOOKKEEPER-700:
---
SUCCESS: Integrated in bookkeeper-trunk #424 (See
[https://builds.apache.org/job/bookkeeper-trunk/424/])
BOOKKEEPER-700: GarbageCollectorThread exsiting with
ArrayIndexOutOfBoundsException (rakeshr via ivank) (ivank: rev 1537130)
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/GarbageCollectorThread.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/CompactionTest.java
GarbageCollectorThread exsiting with ArrayIndexOutOfBoundsException
---
Key: BOOKKEEPER-700
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-700
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 4.3.0
Attachments: 0001-BOOKKEEPER-700.patch, 0002-BOOKKEEPER-700.patch
After completing compaction, GarbageCollectorThread will do flush any
outstanding offsets. When there is no offset present, its throwing following
exception and exiting.
{code}
2013-10-30 11:37:20,944 - ERROR -
[GarbageCollectorThread:NIOServerCnxnFactory$1@49] - Thread
Thread[GarbageCollectorThread,5,main] died
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.waitEntrylogFlushed(GarbageCollectorThread.java:151)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread$CompactionScannerFactory.flush(GarbageCollectorThread.java:175)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.doCompactEntryLogs(GarbageCollectorThread.java:400)
at
org.apache.bookkeeper.bookie.GarbageCollectorThread.run(GarbageCollectorThread.java:309)
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (BOOKKEEPER-429) Provide separate read and write threads in the bookkeeper server
[ https://issues.apache.org/jira/browse/BOOKKEEPER-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-429: -- Attachment: 0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch rebased to trunk. It shows some test regressions. Provide separate read and write threads in the bookkeeper server Key: BOOKKEEPER-429 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-429 Project: Bookkeeper Issue Type: Improvement Components: bookkeeper-server Affects Versions: 4.2.0 Reporter: Aniruddha Assignee: Aniruddha Fix For: 4.3.0 Attachments: 0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch, BK-429.patch, BOOKKEEPER-429.diff, BOOKKEEPER-429.diff The current bookkeeper server is single threaded. The same thread handles reads and writes. When reads are slow (possibly because of excessive seeks), add entry operations suffer in terms of latencies. Providing separate read and write threads helps in reducing add entry latencies and increasing throughput even when we're facing slow reads. Having a single read thread also results in low disk utilization because seeks can't be ordered efficiently by the OS. Multiple read threads would help in improving the read throughput. Discussion on this can be found at http://mail-archives.apache.org/mod_mbox/zookeeper-bookkeeper-dev/201209.mbox/%3ccaolhydqpzn-v10zynfwud_h0qzrxtmjgttx7a9eofohyyty...@mail.gmail.com%3e Reviewboard : https://reviews.apache.org/r/7560/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (BOOKKEEPER-429) Provide separate read and write threads in the bookkeeper server
[
https://issues.apache.org/jira/browse/BOOKKEEPER-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809900#comment-13809900
]
Rakesh R commented on BOOKKEEPER-429:
-
Failure reason:- In the patch, its defined the number of worker threads to
zero. While creating threadpool by Journal, it passes this configured value to
the threadpool executor and is causing the exception. Is there any specific
reason to set the configuration as zero.
{code}
public SlowBookieTest() {
super(4);
+baseConf.setNumAddWorkerThreads(0);
+baseConf.setNumReadWorkerThreads(0);
}
{code}
Thread pool expects a non-zero +ve number. Otw will throw exception as follows:
{code}
ThreadPoolExecutor.java
if (corePoolSize 0 ||
maximumPoolSize = 0 ||
maximumPoolSize corePoolSize ||
keepAliveTime 0)
throw new IllegalArgumentException();
{code}
Provide separate read and write threads in the bookkeeper server
Key: BOOKKEEPER-429
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-429
Project: Bookkeeper
Issue Type: Improvement
Components: bookkeeper-server
Affects Versions: 4.2.0
Reporter: Aniruddha
Assignee: Aniruddha
Fix For: 4.3.0
Attachments:
0001-BOOKKEEPER-429-Provide-separate-read-and-write-threa.patch,
BK-429.patch, BOOKKEEPER-429.diff, BOOKKEEPER-429.diff
The current bookkeeper server is single threaded. The same thread handles
reads and writes. When reads are slow (possibly because of excessive seeks),
add entry operations suffer in terms of latencies. Providing separate read
and write threads helps in reducing add entry latencies and increasing
throughput even when we're facing slow reads. Having a single read thread
also results in low disk utilization because seeks can't be ordered
efficiently by the OS. Multiple read threads would help in improving the read
throughput.
Discussion on this can be found at
http://mail-archives.apache.org/mod_mbox/zookeeper-bookkeeper-dev/201209.mbox/%3ccaolhydqpzn-v10zynfwud_h0qzrxtmjgttx7a9eofohyyty...@mail.gmail.com%3e
Reviewboard : https://reviews.apache.org/r/7560/
--
This message was sent by Atlassian JIRA
(v6.1#6144)
