ZooKeeper-trunk-ibm6 - Build # 595 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-ibm6/595/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 353819 lines...] [junit] 2014-08-25 09:34:21,344 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2014-08-25 09:34:21,346 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-08-25 09:34:21,347 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-08-25 09:34:21,347 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2014-08-25 09:34:21,348 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-08-25 09:34:21,349 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-08-25 09:34:21,349 [myid:] - INFO [main:ZooKeeperServer@781] - minSessionTimeout set to 6000 [junit] 2014-08-25 09:34:21,349 [myid:] - INFO [main:ZooKeeperServer@790] - maxSessionTimeout set to 6 [junit] 2014-08-25 09:34:21,350 [myid:] - INFO [main:ZooKeeperServer@152] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test1935647796284405141.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test1935647796284405141.junit.dir/version-2 [junit] 2014-08-25 09:34:21,351 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test1935647796284405141.junit.dir/version-2/snapshot.b [junit] 2014-08-25 09:34:21,354 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test1935647796284405141.junit.dir/version-2/snapshot.b [junit] 2014-08-25 09:34:21,356 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-08-25 09:34:21,357 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:40225 [junit] 2014-08-25 09:34:21,358 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:40225 [junit] 2014-08-25 09:34:21,359 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-08-25 09:34:21,359 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:40225 (no session established for client) [junit] 2014-08-25 09:34:21,360 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-08-25 09:34:21,363 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-08-25 09:34:21,364 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2014-08-25 09:34:21,364 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-08-25 09:34:21,364 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2014-08-25 09:34:21,365 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 4981 [junit] 2014-08-25 09:34:21,365 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 40 [junit] 2014-08-25 09:34:21,365 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-08-25 09:34:21,366 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-08-25 09:34:21,392 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x1480c84297e closed [junit] 2014-08-25 09:34:21,392 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-08-25 09:34:21,392 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-08-25 09:34:21,398 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2014-08-25 09:34:21,398 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2014-08-25 09:34:21,398 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-08-25 09:34:21,398 [myid:] - INFO
ZooKeeper-trunk-jdk7 - Build # 957 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-jdk7/957/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 336527 lines...] [junit] 2014-08-25 10:14:08,510 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-08-25 10:14:08,510 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-08-25 10:14:08,510 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2014-08-25 10:14:08,510 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-08-25 10:14:08,511 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-08-25 10:14:08,511 [myid:] - INFO [main:ZooKeeperServer@781] - minSessionTimeout set to 6000 [junit] 2014-08-25 10:14:08,511 [myid:] - INFO [main:ZooKeeperServer@790] - maxSessionTimeout set to 6 [junit] 2014-08-25 10:14:08,511 [myid:] - INFO [main:ZooKeeperServer@152] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test4307752103067218762.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test4307752103067218762.junit.dir/version-2 [junit] 2014-08-25 10:14:08,512 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test4307752103067218762.junit.dir/version-2/snapshot.b [junit] 2014-08-25 10:14:08,514 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test4307752103067218762.junit.dir/version-2/snapshot.b [junit] 2014-08-25 10:14:08,516 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-08-25 10:14:08,516 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:43562 [junit] 2014-08-25 10:14:08,517 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:43562 [junit] 2014-08-25 10:14:08,517 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-08-25 10:14:08,518 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:43562 (no session established for client) [junit] 2014-08-25 10:14:08,518 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-08-25 10:14:08,520 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-08-25 10:14:08,520 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2014-08-25 10:14:08,520 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-08-25 10:14:08,520 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2014-08-25 10:14:08,520 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 18084 [junit] 2014-08-25 10:14:08,521 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2014-08-25 10:14:08,521 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-08-25 10:14:08,521 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-08-25 10:14:08,589 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x1480ca896be closed [junit] 2014-08-25 10:14:08,589 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-08-25 10:14:08,589 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-08-25 10:14:08,589 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2014-08-25 10:14:08,589 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2014-08-25 10:14:08,590 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-08-25 10:14:08,590 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit]
ZooKeeper-trunk-jdk8 - Build # 120 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/120/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 337592 lines...] [junit] 2014-08-25 10:50:03,298 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-08-25 10:50:03,299 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-08-25 10:50:03,299 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2014-08-25 10:50:03,299 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-08-25 10:50:03,300 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-08-25 10:50:03,300 [myid:] - INFO [main:ZooKeeperServer@781] - minSessionTimeout set to 6000 [junit] 2014-08-25 10:50:03,300 [myid:] - INFO [main:ZooKeeperServer@790] - maxSessionTimeout set to 6 [junit] 2014-08-25 10:50:03,300 [myid:] - INFO [main:ZooKeeperServer@152] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5309434964663654287.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5309434964663654287.junit.dir/version-2 [junit] 2014-08-25 10:50:03,301 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5309434964663654287.junit.dir/version-2/snapshot.b [junit] 2014-08-25 10:50:03,304 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test5309434964663654287.junit.dir/version-2/snapshot.b [junit] 2014-08-25 10:50:03,310 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-08-25 10:50:03,310 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:53828 [junit] 2014-08-25 10:50:03,312 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:53828 [junit] 2014-08-25 10:50:03,312 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-08-25 10:50:03,312 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:53828 (no session established for client) [junit] 2014-08-25 10:50:03,312 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-08-25 10:50:03,314 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-08-25 10:50:03,314 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2014-08-25 10:50:03,314 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-08-25 10:50:03,315 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2014-08-25 10:50:03,315 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 3484 [junit] 2014-08-25 10:50:03,315 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2014-08-25 10:50:03,315 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-08-25 10:50:03,316 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-08-25 10:50:03,372 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x1480cc977da closed [junit] 2014-08-25 10:50:03,372 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-08-25 10:50:03,372 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-08-25 10:50:03,373 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2014-08-25 10:50:03,373 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-08-25 10:50:03,373 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-08-25 10:50:03,373 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit]
ZooKeeper_branch34_jdk7 - Build # 624 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/624/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 419 lines...] Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.4 failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:339) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:328) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:482) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157) ... 13 more Caused by: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.4 failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 35 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.4' svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 34 more Caused by: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.4' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775) ... 35 more Caused by: svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:514) ... 35 more Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:146) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:73) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:280) at
ZooKeeper_branch35_jdk7 - Build # 23 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/23/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 419 lines...] Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.5 failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:339) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:328) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:482) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157) ... 13 more Caused by: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.5 failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 35 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.5' svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 34 more Caused by: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.5' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775) ... 35 more Caused by: svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:514) ... 35 more Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:146) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:73) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:280) at
ZooKeeper-trunk - Build # 2418 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk/2418/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 320929 lines...] [junit] 2014-08-25 11:11:56,827 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/test/tmp/test3633642868755256597.junit.dir/version-2/snapshot.b [junit] 2014-08-25 11:11:56,829 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-08-25 11:11:56,830 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:35109 [junit] 2014-08-25 11:11:56,832 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:35109 [junit] 2014-08-25 11:11:56,832 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-08-25 11:11:56,832 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:35109 (no session established for client) [junit] 2014-08-25 11:11:56,833 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-08-25 11:11:56,835 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-08-25 11:11:56,835 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2014-08-25 11:11:56,835 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-08-25 11:11:56,836 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2014-08-25 11:11:56,836 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 83946 [junit] 2014-08-25 11:11:56,836 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2014-08-25 11:11:56,837 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-08-25 11:11:56,837 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-08-25 11:11:56,874 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x1480cdd8268 closed [junit] 2014-08-25 11:11:56,874 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-08-25 11:11:56,874 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-08-25 11:11:56,874 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2014-08-25 11:11:56,875 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-08-25 11:11:56,875 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-08-25 11:11:56,875 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2014-08-25 11:11:56,876 [myid:] - INFO [main:ZooKeeperServer@443] - shutting down [junit] 2014-08-25 11:11:56,876 [myid:] - INFO [main:SessionTrackerImpl@231] - Shutting down [junit] 2014-08-25 11:11:56,876 [myid:] - INFO [main:PrepRequestProcessor@973] - Shutting down [junit] 2014-08-25 11:11:56,877 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2014-08-25 11:11:56,877 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop! [junit] 2014-08-25 11:11:56,878 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2014-08-25 11:11:56,878 [myid:] - INFO [main:FinalRequestProcessor@476] - shutdown of request processor complete [junit] 2014-08-25 11:11:56,878 [myid:] - INFO [main:MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree] [junit] 2014-08-25 11:11:56,879 [myid:] - INFO [main:MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port-1] [junit] 2014-08-25 11:11:56,879 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-08-25 11:11:56,880 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2014-08-25 11:11:56,884 [myid:] - INFO [main:ClientBase@545] - fdcount after test is: 46 at start it was 33 [junit] 2014-08-25 11:11:56,885 [myid:] - INFO [main:ClientBase@547] - sleeping for 20 secs [junit] 2014-08-25 11:11:56,886
ZooKeeper-trunk-openjdk7 - Build # 547 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/547/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 419 lines...] Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repos/asf/zookeeper/trunk failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:339) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:328) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:482) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157) ... 13 more Caused by: svn: E175002: OPTIONS /repos/asf/zookeeper/trunk failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 35 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/trunk' svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 34 more Caused by: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/trunk' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775) ... 35 more Caused by: svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:514) ... 35 more Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:146) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:73) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:280) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:451) ... 35 more
[jira] [Updated] (ZOOKEEPER-1660) Add documentation for dynamic reconfiguration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reed Wanderman-Milne updated ZOOKEEPER-1660: Attachment: ZOOKEEPER-1660-v3.patch Add documentation for dynamic reconfiguration - Key: ZOOKEEPER-1660 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1660 Project: ZooKeeper Issue Type: Sub-task Components: documentation Affects Versions: 3.5.0 Reporter: Alexander Shraer Assignee: Reed Wanderman-Milne Priority: Blocker Fix For: 3.5.0 Attachments: ZOOKEEPER-1660-v2.patch, ZOOKEEPER-1660-v3.patch, ZOOKEEPER-1660.patch Update user manual with reconfiguration info. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ZOOKEEPER-1660) Add documentation for dynamic reconfiguration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109669#comment-14109669 ] Reed Wanderman-Milne commented on ZOOKEEPER-1660: - Hi Alex, That was a good change, the overview is much clearer now. Note that I had to format the paper citation slightly, since it appears Docbooks doesn't support line breaks. Tell me if there are any more changes to the Google Doc. The patch contains a reference to the reconfig page from the Administrator's guide (in the section Configuration Parameters), so a reader should be able to figure out how to upgrade to 3.5.0. Add documentation for dynamic reconfiguration - Key: ZOOKEEPER-1660 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1660 Project: ZooKeeper Issue Type: Sub-task Components: documentation Affects Versions: 3.5.0 Reporter: Alexander Shraer Assignee: Reed Wanderman-Milne Priority: Blocker Fix For: 3.5.0 Attachments: ZOOKEEPER-1660-v2.patch, ZOOKEEPER-1660-v3.patch, ZOOKEEPER-1660.patch Update user manual with reconfiguration info. -- This message was sent by Atlassian JIRA (v6.2#6252)
Failed: ZOOKEEPER-1660 PreCommit Build #2299
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1660 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2299/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 318600 lines...] [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +0 tests included. The patch appears to be a documentation patch that doesn't require tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] -1 core tests. The patch failed 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/2299//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2299//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2299//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] 7075f20263a7c57d3f6274df076d919e56126836 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:1713: exec returned: 1 Total time: 40 minutes 0 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2179 Archived 7 artifacts Archive block size is 32768 Received 0 blocks and 547195 bytes Compression is 0.0% Took 2.9 sec Recording test results Description set: ZOOKEEPER-1660 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 2 tests failed. REGRESSION: org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig Error Message: waiting for server 2 being up Stack Trace: junit.framework.AssertionFailedError: waiting for server 2 being up at org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52) FAILED: org.apache.zookeeper.test.NioNettySuiteHammerTest.testHammer Error Message: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit. Stack Trace: junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
[jira] [Commented] (ZOOKEEPER-1660) Add documentation for dynamic reconfiguration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109724#comment-14109724 ] Hadoop QA commented on ZOOKEEPER-1660: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12664205/ZOOKEEPER-1660-v3.patch against trunk revision 1620111. +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2299//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2299//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2299//console This message is automatically generated. Add documentation for dynamic reconfiguration - Key: ZOOKEEPER-1660 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1660 Project: ZooKeeper Issue Type: Sub-task Components: documentation Affects Versions: 3.5.0 Reporter: Alexander Shraer Assignee: Reed Wanderman-Milne Priority: Blocker Fix For: 3.5.0 Attachments: ZOOKEEPER-1660-v2.patch, ZOOKEEPER-1660-v3.patch, ZOOKEEPER-1660.patch Update user manual with reconfiguration info. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ZOOKEEPER-2016) Automate client-side rebalancing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongchao Deng updated ZOOKEEPER-2016: - Attachment: draft.patch [~shralex] I did a draft. Is this what you are expecting? Automate client-side rebalancing Key: ZOOKEEPER-2016 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016 Project: ZooKeeper Issue Type: Improvement Reporter: Hongchao Deng Attachments: draft.patch ZOOKEEPER-1355 introduced client-side rebalancing, which is implemented in both the C and Java client libraries. However, it requires the client to detect a configuration change and call updateServerList with the new connection string (see reconfig manual). It may be better if the client just indicates that he is interested in this feature when creating a ZK handle and we'll detect configuration changes and invoke updateServerList for him underneath the hood. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ZOOKEEPER-2016) Automate client-side rebalancing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongchao Deng updated ZOOKEEPER-2016: - Attachment: (was: draft.patch) Automate client-side rebalancing Key: ZOOKEEPER-2016 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016 Project: ZooKeeper Issue Type: Improvement Reporter: Hongchao Deng ZOOKEEPER-1355 introduced client-side rebalancing, which is implemented in both the C and Java client libraries. However, it requires the client to detect a configuration change and call updateServerList with the new connection string (see reconfig manual). It may be better if the client just indicates that he is interested in this feature when creating a ZK handle and we'll detect configuration changes and invoke updateServerList for him underneath the hood. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ZOOKEEPER-2016) Automate client-side rebalancing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongchao Deng updated ZOOKEEPER-2016: - Attachment: draft.patch Automate client-side rebalancing Key: ZOOKEEPER-2016 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016 Project: ZooKeeper Issue Type: Improvement Reporter: Hongchao Deng Attachments: draft.patch ZOOKEEPER-1355 introduced client-side rebalancing, which is implemented in both the C and Java client libraries. However, it requires the client to detect a configuration change and call updateServerList with the new connection string (see reconfig manual). It may be better if the client just indicates that he is interested in this feature when creating a ZK handle and we'll detect configuration changes and invoke updateServerList for him underneath the hood. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ZOOKEEPER-2016) Automate client-side rebalancing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109752#comment-14109752 ] Alexander Shraer commented on ZOOKEEPER-2016: - Hi Hongchao, thanks a lot for taking this on! I'll take a closer look later, but first a high level comment - the rebalancing callback is not only done for the client that invoked reconfig. All clients set a watch on the special znode, and when one client invokes reconfig, all these watches will be triggered. This shouldn't be tied to the response of reconfig rather to the watches set on the znode, please see the example at the end of the Google Doc. My thought was that the client side library will have some kind of handler for these watch events. The complication is that I'm not sure if currently the client side library is intercepting events in this way. A second complication is that we only want to intercept watches fired on the special reconfig znode but pass all other events to the client code. I'm not sure exactly how this can be done. Automate client-side rebalancing Key: ZOOKEEPER-2016 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016 Project: ZooKeeper Issue Type: Improvement Reporter: Hongchao Deng Attachments: draft.patch ZOOKEEPER-1355 introduced client-side rebalancing, which is implemented in both the C and Java client libraries. However, it requires the client to detect a configuration change and call updateServerList with the new connection string (see reconfig manual). It may be better if the client just indicates that he is interested in this feature when creating a ZK handle and we'll detect configuration changes and invoke updateServerList for him underneath the hood. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ZOOKEEPER-2016) Automate client-side rebalancing
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110044#comment-14110044 ] Hongchao Deng commented on ZOOKEEPER-2016: -- [~shralex] A little depth into details. Does the completion of reconfig guarantee the completion of updates on CONFIG_ZNODE? If so, my suggestion is to do updateServerList after reconfig is done. Automate client-side rebalancing Key: ZOOKEEPER-2016 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016 Project: ZooKeeper Issue Type: Improvement Reporter: Hongchao Deng Attachments: draft.patch ZOOKEEPER-1355 introduced client-side rebalancing, which is implemented in both the C and Java client libraries. However, it requires the client to detect a configuration change and call updateServerList with the new connection string (see reconfig manual). It may be better if the client just indicates that he is interested in this feature when creating a ZK handle and we'll detect configuration changes and invoke updateServerList for him underneath the hood. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ZOOKEEPER-2019) Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raul Gutierrez Segales updated ZOOKEEPER-2019:
--
Attachment: ZOOKEEPER-2019.patch
Thanks for the quick review [~shralex], I've addressed the items you mentioned.
Unhandled exception when setting invalid limits data in
/zookeeper/quota/some/path/zookeeper_limits
Key: ZOOKEEPER-2019
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2019
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
Attachments: ZOOKEEPER-2019.patch, ZOOKEEPER-2019.patch
If you have quotas properly set for a given path, i.e.:
{noformat}
create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
{noformat}
and then you update the limits znode with bogus data, i.e.:
{noformat}
set /zookeeper/quota/test/zookeeper_limits ''
{noformat}
you'll crash the cluster because IllegalArgumentException isn't handled when
dealing with quotas znodes:
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425
We should handle IllegalArgumentException. Optionally, we should also throw
BadArgumentsException from PrepRequestProcessor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Failed: ZOOKEEPER-2019 PreCommit Build #2300
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2019 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 317923 lines...] [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] -1 core tests. The patch failed 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/2300//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//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] 04652440d589d7730e001fb0bffad30fd1664789 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:1713: exec returned: 1 Total time: 39 minutes 8 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2179 Archived 7 artifacts Archive block size is 32768 Received 0 blocks and 547197 bytes Compression is 0.0% Took 5.2 sec Recording test results Description set: ZOOKEEPER-2019 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 2 tests failed. REGRESSION: org.apache.zookeeper.test.ReconfigTest.testPortChange Error Message: expected:test[1] but was:test[0] Stack Trace: junit.framework.AssertionFailedError: expected:test[1] but was:test[0] at org.apache.zookeeper.test.ReconfigTest.testNormalOperation(ReconfigTest.java:151) at org.apache.zookeeper.test.ReconfigTest.testPortChange(ReconfigTest.java:600) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52) FAILED: org.apache.zookeeper.test.NioNettySuiteHammerTest.testHammer Error Message: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit. Stack Trace: junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
[jira] [Commented] (ZOOKEEPER-2019) Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110223#comment-14110223
]
Hadoop QA commented on ZOOKEEPER-2019:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12664289/ZOOKEEPER-2019.patch
against trunk revision 1620111.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//console
This message is automatically generated.
Unhandled exception when setting invalid limits data in
/zookeeper/quota/some/path/zookeeper_limits
Key: ZOOKEEPER-2019
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2019
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
Attachments: ZOOKEEPER-2019.patch, ZOOKEEPER-2019.patch
If you have quotas properly set for a given path, i.e.:
{noformat}
create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
{noformat}
and then you update the limits znode with bogus data, i.e.:
{noformat}
set /zookeeper/quota/test/zookeeper_limits ''
{noformat}
you'll crash the cluster because IllegalArgumentException isn't handled when
dealing with quotas znodes:
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425
We should handle IllegalArgumentException. Optionally, we should also throw
BadArgumentsException from PrepRequestProcessor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (ZOOKEEPER-2019) Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110236#comment-14110236
]
Raul Gutierrez Segales commented on ZOOKEEPER-2019:
---
Failures seem unrelated:
{noformat}
[exec] [junit] 2014-08-26 02:53:32,839 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED
testReadArrayOffsetLength_LengthTooLarge
[exec] [junit] 2014-08-26 02:56:13,636 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED
testTooManySnapshotsNonessential
[exec] [junit] 2014-08-26 02:56:13,641 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED
testTooManySnapshotsEssential
[exec] [junit] 2014-08-26 02:56:13,650 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED
testTryWithResourceThrottle
[exec] [junit] Test org.apache.zookeeper.test.NioNettySuiteHammerTest
FAILED (crashed)
[exec] [junit] 2014-08-26 03:21:37,644 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED
testPortChange
[exec] [junit] 2014-08-26 03:21:37,683 [myid:] - INFO
[main:ZKTestCase$1@70] - FAILED testPortChange
[exec] [junit] Test org.apache.zookeeper.test.ReconfigTest FAILED
[exec] [junit] 2014-08-26 03:24:11,194 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED
testTwoInvalidHostAddresses
[exec] BUILD FAILED
{noformat}
Unhandled exception when setting invalid limits data in
/zookeeper/quota/some/path/zookeeper_limits
Key: ZOOKEEPER-2019
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2019
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
Attachments: ZOOKEEPER-2019.patch, ZOOKEEPER-2019.patch
If you have quotas properly set for a given path, i.e.:
{noformat}
create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
{noformat}
and then you update the limits znode with bogus data, i.e.:
{noformat}
set /zookeeper/quota/test/zookeeper_limits ''
{noformat}
you'll crash the cluster because IllegalArgumentException isn't handled when
dealing with quotas znodes:
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425
We should handle IllegalArgumentException. Optionally, we should also throw
BadArgumentsException from PrepRequestProcessor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (ZOOKEEPER-2019) Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shraer updated ZOOKEEPER-2019:
Attachment: ZOOKEEPER-2019-ver1.patch
Thanks Raul! I made a small change to the code that was doing the parsing, take
a look. The motivation is to check not only the numbers but also the strings
'count' and 'bytes' and throw an exception if something is wrong.
Unhandled exception when setting invalid limits data in
/zookeeper/quota/some/path/zookeeper_limits
Key: ZOOKEEPER-2019
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2019
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
Attachments: ZOOKEEPER-2019-ver1.patch, ZOOKEEPER-2019.patch,
ZOOKEEPER-2019.patch
If you have quotas properly set for a given path, i.e.:
{noformat}
create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
{noformat}
and then you update the limits znode with bogus data, i.e.:
{noformat}
set /zookeeper/quota/test/zookeeper_limits ''
{noformat}
you'll crash the cluster because IllegalArgumentException isn't handled when
dealing with quotas znodes:
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425
We should handle IllegalArgumentException. Optionally, we should also throw
BadArgumentsException from PrepRequestProcessor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (ZOOKEEPER-2019) Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110286#comment-14110286
]
Raul Gutierrez Segales commented on ZOOKEEPER-2019:
---
This indeed reads much better, thanks [~shralex]! Much easier to extend (i.e.:
I suspect we'll want to add more things like write/read rates, etc.) too.
Unhandled exception when setting invalid limits data in
/zookeeper/quota/some/path/zookeeper_limits
Key: ZOOKEEPER-2019
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2019
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
Attachments: ZOOKEEPER-2019-ver1.patch, ZOOKEEPER-2019.patch,
ZOOKEEPER-2019.patch
If you have quotas properly set for a given path, i.e.:
{noformat}
create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
{noformat}
and then you update the limits znode with bogus data, i.e.:
{noformat}
set /zookeeper/quota/test/zookeeper_limits ''
{noformat}
you'll crash the cluster because IllegalArgumentException isn't handled when
dealing with quotas znodes:
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425
We should handle IllegalArgumentException. Optionally, we should also throw
BadArgumentsException from PrepRequestProcessor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Failed: ZOOKEEPER-2019 PreCommit Build #2301
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2019 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 314801 lines...] [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] -1 core tests. The patch failed 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/2301//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//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] 9d8f66bac3a3206a2de3e1905185c567ce29d3f1 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:1713: exec returned: 1 Total time: 39 minutes 35 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2179 Archived 7 artifacts Archive block size is 32768 Received 0 blocks and 547195 bytes Compression is 0.0% Took 2.7 sec Recording test results Description set: ZOOKEEPER-2019 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 2 tests failed. REGRESSION: org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig Error Message: waiting for server 2 being up Stack Trace: junit.framework.AssertionFailedError: waiting for server 2 being up at org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529) at org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52) FAILED: org.apache.zookeeper.test.NioNettySuiteHammerTest.testHammer Error Message: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit. Stack Trace: junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
[jira] [Commented] (ZOOKEEPER-2019) Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110311#comment-14110311
]
Hadoop QA commented on ZOOKEEPER-2019:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12664311/ZOOKEEPER-2019-ver1.patch
against trunk revision 1620111.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//console
This message is automatically generated.
Unhandled exception when setting invalid limits data in
/zookeeper/quota/some/path/zookeeper_limits
Key: ZOOKEEPER-2019
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2019
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
Attachments: ZOOKEEPER-2019-ver1.patch, ZOOKEEPER-2019.patch,
ZOOKEEPER-2019.patch
If you have quotas properly set for a given path, i.e.:
{noformat}
create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
{noformat}
and then you update the limits znode with bogus data, i.e.:
{noformat}
set /zookeeper/quota/test/zookeeper_limits ''
{noformat}
you'll crash the cluster because IllegalArgumentException isn't handled when
dealing with quotas znodes:
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425
We should handle IllegalArgumentException. Optionally, we should also throw
BadArgumentsException from PrepRequestProcessor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (BOOKKEEPER-736) Stats for AutoRecovery
[ https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110313#comment-14110313 ] Rakesh R commented on BOOKKEEPER-736: - Thanks Sijie, latest patch looks better. There are few more comments from me. Sorry, I failed to include this previously. # It would be better to categorize success and failure based on the re-replica operation. For this, please modify rereplicate(long ledgerIdToReplicate) method by returning boolean status. Then return 'true' only if the underreplicationManager.markLedgerReplicated(ledgerIdToReplicate); call succeeds, all other places we can return 'false'. # Should we retain the existing constructors for ReplicationWorker, AuditorElector. I couldn't see any usage of these, please remove. Stats for AutoRecovery -- Key: BOOKKEEPER-736 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736 Project: Bookkeeper Issue Type: New Feature Components: bookkeeper-auto-recovery Reporter: Rakesh R Assignee: Sijie Guo Fix For: 4.3.0 Attachments: BOOKKEEPER-736.patch, BOOKKEEPER-736.v2.patch, BOOKKEEPER-736.v3.patch, Prototype-JMX-beans-for-standalone-autorecovery-process.png Idea of this JIRA is to provide jmx interfaces to get the statistics of the auto recovery activities. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ZOOKEEPER-2019) Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110320#comment-14110320
]
Alexander Shraer commented on ZOOKEEPER-2019:
-
+1, failures look unrelated.
Unhandled exception when setting invalid limits data in
/zookeeper/quota/some/path/zookeeper_limits
Key: ZOOKEEPER-2019
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2019
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
Attachments: ZOOKEEPER-2019-ver1.patch, ZOOKEEPER-2019.patch,
ZOOKEEPER-2019.patch
If you have quotas properly set for a given path, i.e.:
{noformat}
create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
{noformat}
and then you update the limits znode with bogus data, i.e.:
{noformat}
set /zookeeper/quota/test/zookeeper_limits ''
{noformat}
you'll crash the cluster because IllegalArgumentException isn't handled when
dealing with quotas znodes:
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425
We should handle IllegalArgumentException. Optionally, we should also throw
BadArgumentsException from PrepRequestProcessor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (BOOKKEEPER-736) Stats for AutoRecovery
[ https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108817#comment-14108817 ] Sijie Guo commented on BOOKKEEPER-736: -- k. I will fix the rereplicate stat. for the urledgers counter, I don't want to add this counter. as it is hard and doesn't make any sense to collect an inaccurate counter. Stats for AutoRecovery -- Key: BOOKKEEPER-736 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736 Project: Bookkeeper Issue Type: New Feature Components: bookkeeper-auto-recovery Reporter: Rakesh R Assignee: Sijie Guo Fix For: 4.3.0 Attachments: BOOKKEEPER-736.patch, BOOKKEEPER-736.v2.patch, Prototype-JMX-beans-for-standalone-autorecovery-process.png Idea of this JIRA is to provide jmx interfaces to get the statistics of the auto recovery activities. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (BOOKKEEPER-736) Stats for AutoRecovery
[ https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108833#comment-14108833 ] Rakesh R commented on BOOKKEEPER-736: - Make sense +1. Stats for AutoRecovery -- Key: BOOKKEEPER-736 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736 Project: Bookkeeper Issue Type: New Feature Components: bookkeeper-auto-recovery Reporter: Rakesh R Assignee: Sijie Guo Fix For: 4.3.0 Attachments: BOOKKEEPER-736.patch, BOOKKEEPER-736.v2.patch, Prototype-JMX-beans-for-standalone-autorecovery-process.png Idea of this JIRA is to provide jmx interfaces to get the statistics of the auto recovery activities. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (BOOKKEEPER-736) Stats for AutoRecovery
[ https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-736: - Attachment: BOOKKEEPER-736.v3.patch attach a new patch improving re-replicate stat collection Stats for AutoRecovery -- Key: BOOKKEEPER-736 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736 Project: Bookkeeper Issue Type: New Feature Components: bookkeeper-auto-recovery Reporter: Rakesh R Assignee: Sijie Guo Fix For: 4.3.0 Attachments: BOOKKEEPER-736.patch, BOOKKEEPER-736.v2.patch, BOOKKEEPER-736.v3.patch, Prototype-JMX-beans-for-standalone-autorecovery-process.png Idea of this JIRA is to provide jmx interfaces to get the statistics of the auto recovery activities. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (BOOKKEEPER-736) Stats for AutoRecovery
[
https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108937#comment-14108937
]
Hadoop QA commented on BOOKKEEPER-736:
--
Testing JIRA BOOKKEEPER-736
Patch
[BOOKKEEPER-736.v3.patch|https://issues.apache.org/jira/secure/attachment/12664111/BOOKKEEPER-736.v3.patch]
downloaded at Mon Aug 25 08:17:54 UTC 2014
{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:red}WARNING{color}: the current HEAD has 23 Javadoc warning(s)
{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}WARNING: the current HEAD has Findbugs warning(s), they should
be addressed ASAP{color}
{color:red}-1 TESTS{color}
.Tests run: 745
.Tests failed: 0
.Tests errors: 1
.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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/681/
Stats for AutoRecovery
--
Key: BOOKKEEPER-736
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736
Project: Bookkeeper
Issue Type: New Feature
Components: bookkeeper-auto-recovery
Reporter: Rakesh R
Assignee: Sijie Guo
Fix For: 4.3.0
Attachments: BOOKKEEPER-736.patch, BOOKKEEPER-736.v2.patch,
BOOKKEEPER-736.v3.patch,
Prototype-JMX-beans-for-standalone-autorecovery-process.png
Idea of this JIRA is to provide jmx interfaces to get the statistics of the
auto recovery activities.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (BOOKKEEPER-736) Stats for AutoRecovery
[
https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109000#comment-14109000
]
Hadoop QA commented on BOOKKEEPER-736:
--
Testing JIRA BOOKKEEPER-736
Patch
[BOOKKEEPER-736.v3.patch|https://issues.apache.org/jira/secure/attachment/12664111/BOOKKEEPER-736.v3.patch]
downloaded at Mon Aug 25 09:31:44 UTC 2014
{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:red}WARNING{color}: the current HEAD has 23 Javadoc warning(s)
{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}WARNING: the current HEAD has Findbugs warning(s), they should
be addressed ASAP{color}
{color:red}-1 TESTS{color}
.Tests run: 804
.Tests failed: 8
.Tests errors: 10
.The patch failed the following testcases:
.
testAsyncSubscribeWithInvalidSubscriberId[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
.
testSyncUnsubscribeWithInvalidSubscriberId[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
.
testAsyncUnsubscribeWithInvalidSubscriberId[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
.
testSyncHubSubscribeWithInvalidSubscriberId[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
.
testAsyncHubSubscribeWithInvalidSubscriberId[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
.
testSyncHubUnsubscribeWithInvalidSubscriberId[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
.
testAsyncHubUnsubscribeWithInvalidSubscriberId[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
.
testPublishWithBookKeeperError[1](org.apache.hedwig.server.integration.TestHedwigHubSSL)
{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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/682/
Stats for AutoRecovery
--
Key: BOOKKEEPER-736
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736
Project: Bookkeeper
Issue Type: New Feature
Components: bookkeeper-auto-recovery
Reporter: Rakesh R
Assignee: Sijie Guo
Fix For: 4.3.0
Attachments: BOOKKEEPER-736.patch, BOOKKEEPER-736.v2.patch,
BOOKKEEPER-736.v3.patch,
Prototype-JMX-beans-for-standalone-autorecovery-process.png
Idea of this JIRA is to provide jmx interfaces to get the statistics of the
auto recovery activities.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Build failed in Jenkins: bookkeeper-trunk #751
See https://builds.apache.org/job/bookkeeper-trunk/751/ -- [...truncated 773 lines...] Running org.apache.bookkeeper.meta.GcLedgersTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.251 sec Running org.apache.bookkeeper.bookie.LedgerCacheTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.29 sec Running org.apache.bookkeeper.bookie.BookieThreadTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.124 sec Running org.apache.bookkeeper.bookie.TestSyncThread Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.897 sec Running org.apache.bookkeeper.bookie.IndexCorruptionTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.728 sec Running org.apache.bookkeeper.bookie.CompactionTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 38.487 sec Running org.apache.bookkeeper.bookie.BookieInitializationTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.672 sec Running org.apache.bookkeeper.bookie.BookieJournalTest Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.864 sec Running org.apache.bookkeeper.bookie.CreateNewLogTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.341 sec Running org.apache.bookkeeper.bookie.CookieTest Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.936 sec Running org.apache.bookkeeper.bookie.UpgradeTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.52 sec Running org.apache.bookkeeper.bookie.TestLedgerDirsManager Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.223 sec Running org.apache.bookkeeper.bookie.EntryLogTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.385 sec Running org.apache.bookkeeper.bookie.BookieShutdownTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.489 sec Running org.apache.bookkeeper.client.TestWatchEnsembleChange Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.775 sec Running org.apache.bookkeeper.client.RoundRobinDistributionScheduleTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.122 sec Running org.apache.bookkeeper.client.BookKeeperCloseTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.8 sec Running org.apache.bookkeeper.client.ListLedgersTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.718 sec Running org.apache.bookkeeper.client.TestFencing Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.478 sec Running org.apache.bookkeeper.client.BookieWriteLedgerTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.109 sec Running org.apache.bookkeeper.client.BookKeeperTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.769 sec Running org.apache.bookkeeper.client.TestLedgerFragmentReplication Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.351 sec Running org.apache.bookkeeper.client.LedgerCloseTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.513 sec Running org.apache.bookkeeper.client.BookieRecoveryTest Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.604 sec Running org.apache.bookkeeper.client.TestReadTimeout Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.558 sec Running org.apache.bookkeeper.client.LedgerRecoveryTest Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.592 sec Running org.apache.bookkeeper.client.TestTryReadLastConfirmed Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.514 sec Running org.apache.bookkeeper.client.TestSpeculativeRead Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.871 sec Running org.apache.bookkeeper.client.TestLedgerChecker Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.802 sec Running org.apache.bookkeeper.client.TestRackawareEnsemblePlacementPolicy Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.832 sec Running org.apache.bookkeeper.client.SlowBookieTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.798 sec Running org.apache.bookkeeper.util.TestDiskChecker Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.149 sec Running org.apache.bookkeeper.metastore.TestMetaStore Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.273 sec Running org.apache.bookkeeper.test.BookieZKExpireTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.77 sec Running org.apache.bookkeeper.test.ConditionalSetTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.822 sec Running org.apache.bookkeeper.test.ReadOnlyBookieTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.387 sec Running org.apache.bookkeeper.test.ConcurrentLedgerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.484 sec Running
[jira] [Assigned] (BOOKKEEPER-718) AuditorLedgerCheckerTest is flakey
[ https://issues.apache.org/jira/browse/BOOKKEEPER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly reassigned BOOKKEEPER-718: - Assignee: Ivan Kelly AuditorLedgerCheckerTest is flakey -- Key: BOOKKEEPER-718 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-718 Project: Bookkeeper Issue Type: Bug Components: bookkeeper-auto-recovery Reporter: Ivan Kelly Assignee: Ivan Kelly Fix For: 4.3.0 Attachments: error505.txt, error509.txt See: https://builds.apache.org/job/bookkeeper-trunk/505/ https://builds.apache.org/job/bookkeeper-trunk/509 Relevant errors attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (BOOKKEEPER-594) AutoRecovery shutting down on SyncDisconnected
[ https://issues.apache.org/jira/browse/BOOKKEEPER-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109352#comment-14109352 ] Ivan Kelly commented on BOOKKEEPER-594: --- This should go into the next release, as it's part of making bookkeeper availability independent of zookeeper sessions. AutoRecovery shutting down on SyncDisconnected -- Key: BOOKKEEPER-594 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-594 Project: Bookkeeper Issue Type: Bug Components: bookkeeper-auto-recovery Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Critical Fix For: 4.4.0 Attachments: BOOKKEEPER-594.diff Currently the AutoRecovery daemon will shut down on SyncDisconnected. This is the wrong behaviour. It should wait until it gets a expired signal before shutting down. If autoRecoveryDaemonEnabled=true, then the autorecovery deamon is running in the same process as the bookie, the bookie death watcher will take down the bookie at this point also, but as the bookie hasn't shutdown, exit code will be 0, which is confusing to any monitoring app. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (BOOKKEEPER-398) Improving stats collection in bookkeeper
[ https://issues.apache.org/jira/browse/BOOKKEEPER-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109353#comment-14109353 ] Ivan Kelly commented on BOOKKEEPER-398: --- [~hustlmsp] I assume this can be closed now, since the related jiras are in? Improving stats collection in bookkeeper Key: BOOKKEEPER-398 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-398 Project: Bookkeeper Issue Type: Improvement Components: hedwig-server Affects Versions: 4.2.0 Reporter: Aniruddha Assignee: Aniruddha Fix For: 4.3.0 Attachments: BK-398.patch We have been experimenting with using the Twitter stats package (http://twitter.github.com/commons/apidocs/com/twitter/common/stats/package-summary.html) for exporting hedwig stats over HTTP. This is open-sourced under the Apache license. The motivation for this was better logging of percentile latencies and requests-per-second (which are difficult to measure with the current implementation of hedwig stats). Is this something the community would be interested in? If so, I could work on a patch. Reviewboard : https://reviews.apache.org/r/7134/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (BOOKKEEPER-594) AutoRecovery shutting down on SyncDisconnected
[ https://issues.apache.org/jira/browse/BOOKKEEPER-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-594: -- Fix Version/s: (was: 4.3.0) 4.4.0 AutoRecovery shutting down on SyncDisconnected -- Key: BOOKKEEPER-594 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-594 Project: Bookkeeper Issue Type: Bug Components: bookkeeper-auto-recovery Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Critical Fix For: 4.4.0 Attachments: BOOKKEEPER-594.diff Currently the AutoRecovery daemon will shut down on SyncDisconnected. This is the wrong behaviour. It should wait until it gets a expired signal before shutting down. If autoRecoveryDaemonEnabled=true, then the autorecovery deamon is running in the same process as the bookie, the bookie death watcher will take down the bookie at this point also, but as the bookie hasn't shutdown, exit code will be 0, which is confusing to any monitoring app. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (BOOKKEEPER-398) Improving stats collection in bookkeeper
[ https://issues.apache.org/jira/browse/BOOKKEEPER-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo resolved BOOKKEEPER-398. -- Resolution: Fixed Improving stats collection in bookkeeper Key: BOOKKEEPER-398 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-398 Project: Bookkeeper Issue Type: Improvement Components: hedwig-server Affects Versions: 4.2.0 Reporter: Aniruddha Assignee: Aniruddha Fix For: 4.3.0 Attachments: BK-398.patch We have been experimenting with using the Twitter stats package (http://twitter.github.com/commons/apidocs/com/twitter/common/stats/package-summary.html) for exporting hedwig stats over HTTP. This is open-sourced under the Apache license. The motivation for this was better logging of percentile latencies and requests-per-second (which are difficult to measure with the current implementation of hedwig stats). Is this something the community would be interested in? If so, I could work on a patch. Reviewboard : https://reviews.apache.org/r/7134/ -- This message was sent by Atlassian JIRA (v6.2#6252)
