ZooKeeper-trunk-solaris - Build # 703 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/703/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 220322 lines...] [junit] 2013-10-17 09:04:03,680 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2013-10-17 09:04:03,681 [myid:] - INFO [main:ZooKeeperServer@428] - shutting down [junit] 2013-10-17 09:04:03,681 [myid:] - INFO [main:SessionTrackerImpl@183] - Shutting down [junit] 2013-10-17 09:04:03,682 [myid:] - INFO [main:PrepRequestProcessor@972] - Shutting down [junit] 2013-10-17 09:04:03,682 [myid:] - INFO [main:SyncRequestProcessor@190] - Shutting down [junit] 2013-10-17 09:04:03,682 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-10-17 09:04:03,682 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2013-10-17 09:04:03,682 [myid:] - INFO [main:FinalRequestProcessor@442] - shutdown of request processor complete [junit] 2013-10-17 09:04:03,683 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 09:04:03,683 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-17 09:04:03,684 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-17 09:04:03,684 [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/test5986414466485995168.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test5986414466485995168.junit.dir/version-2 [junit] 2013-10-17 09:04:03,685 [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-17 09:04:03,685 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-17 09:04:03,686 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test5986414466485995168.junit.dir/version-2/snapshot.b [junit] 2013-10-17 09:04:03,689 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test5986414466485995168.junit.dir/version-2/snapshot.b [junit] 2013-10-17 09:04:03,690 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 09:04:03,691 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:52939 [junit] 2013-10-17 09:04:03,691 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@828] - Processing stat command from /127.0.0.1:52939 [junit] 2013-10-17 09:04:03,692 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@677] - Stat command output [junit] 2013-10-17 09:04:03,692 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@999] - Closed socket connection for client /127.0.0.1:52939 (no session established for client) [junit] 2013-10-17 09:04:03,692 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-17 09:04:03,694 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-17 09:04:03,694 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-17 09:04:03,694 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-17 09:04:03,694 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-17 09:04:03,694 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-17 09:04:03,695 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-17 09:04:03,775 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down [junit] 2013-10-17 09:04:03,775 [myid:] - INFO [main:ZooKeeper@777] - Session: 0x141c5a84da4 closed [junit] 2013-10-17 09:04:03,776 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-17 09:04:03,776 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServe
ZooKeeper-3.4-WinVS2008_java - Build # 327 - Still Failing
See https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java/327/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 208298 lines...] [junit] 2013-10-17 11:16:02,783 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:03,085 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:03,387 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:03,689 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:03,990 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:04,292 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:04,594 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:04,896 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:05,197 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:05,499 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:16:06,492 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-17 11:16:06,507 [myid:] - INFO [main:ZKTestCase$1@65] - FAILED testQuota [junit] junit.framework.AssertionFailedError: expected [0x141c5e9fca90001] expected:<1> but was:<0> [junit] at junit.framework.Assert.fail(Assert.java:47) [junit] at junit.framework.Assert.failNotEquals(Assert.java:283) [junit] at junit.framework.Assert.assertEquals(Assert.java:64) [junit] at junit.framework.Assert.assertEquals(Assert.java:195) [junit] at org.apache.zookeeper.test.JMXEnv.ensureAll(JMXEnv.java:115) [junit] at org.apache.zookeeper.test.ClientBase.createClient(ClientBase.java:197) [junit] at org.apache.zookeeper.test.ClientBase.createClient(ClientBase.java:171) [junit] at org.apache.zookeeper.test.ClientBase.createClient(ClientBase.java:156) [junit] at org.apache.zookeeper.test.ClientBase.createClient(ClientBase.java:149) [junit] at org.apache.zookeeper.test.ZooKeeperQuotaTest.testQuota(ZooKeeperQuotaTest.java:46) [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:48) [junit] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) [junit] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) [junit] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) [junit] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) [junit] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) [junit] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) [junit] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) [junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:236) [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-17 11:16:06,537 [myid:] - INFO [main:ZKTestCase$1@55] - FINISHED testQuota [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 8.498 sec [junit] Test org.apache.z
ZooKeeper_branch34_jdk7 - Build # 377 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/377/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 204749 lines...] [junit] 2013-10-17 10:24:59,673 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-17 10:24:59,673 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-17 10:24:59,673 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-17 10:24:59,674 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@224] - NIOServerCnxn factory exited run method [junit] 2013-10-17 10:24:59,674 [myid:] - INFO [main:ZooKeeperServer@443] - shutting down [junit] 2013-10-17 10:24:59,674 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2013-10-17 10:24:59,674 [myid:] - INFO [main:PrepRequestProcessor@761] - Shutting down [junit] 2013-10-17 10:24:59,674 [myid:] - INFO [main:SyncRequestProcessor@190] - Shutting down [junit] 2013-10-17 10:24:59,674 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2013-10-17 10:24:59,675 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2013-10-17 10:24:59,675 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2013-10-17 10:24:59,675 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 10:24:59,676 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-17 10:24:59,677 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-17 10:24:59,677 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7801107576036089190.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7801107576036089190.junit.dir/version-2 [junit] 2013-10-17 10:24:59,677 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-17 10:24:59,678 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7801107576036089190.junit.dir/version-2/snapshot.b [junit] 2013-10-17 10:24:59,680 [myid:] - INFO [main:FileTxnSnapLog@240] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7801107576036089190.junit.dir/version-2/snapshot.b [junit] 2013-10-17 10:24:59,682 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 10:24:59,682 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:34343 [junit] 2013-10-17 10:24:59,682 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@817] - Processing stat command from /127.0.0.1:34343 [junit] 2013-10-17 10:24:59,683 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@653] - Stat command output [junit] 2013-10-17 10:24:59,683 [myid:] - INFO [Thread-4:NIOServerCnxn@997] - Closed socket connection for client /127.0.0.1:34343 (no session established for client) [junit] 2013-10-17 10:24:59,683 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-17 10:24:59,684 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-17 10:24:59,685 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-17 10:24:59,685 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-17 10:24:59,685 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-17 10:24:59,685 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-17 10:24:59,685 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-17 10:24:59,760 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x141c5f265bd closed [junit] 2013-10-17 10:24:59,760 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@509] - EventThread shut down [junit] 2013-10-17 10:24:59,760 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-10-17 10:24:59,761 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnF
ZooKeeper-trunk-WinVS2008_java - Build # 575 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008_java/575/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 274557 lines...] [junit] 2013-10-17 11:25:49,210 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-10-17 11:25:49,211 [myid:] - INFO [main:FinalRequestProcessor@442] - shutdown of request processor complete [junit] 2013-10-17 11:25:49,212 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:25:49,643 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1008] - 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-17 11:25:50,203 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-10-17 11:25:50,204 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-10-17 11:25:50,204 [myid:] - INFO [main:ZooKeeperServer@149] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test2237069409898274011.junit.dir\version-2 snapdir f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test2237069409898274011.junit.dir\version-2 [junit] 2013-10-17 11:25:50,217 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 1 selector thread(s), 4 worker threads, and 64 kB direct buffers. [junit] 2013-10-17 11:25:50,218 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-10-17 11:25:50,219 [myid:] - INFO [main:FileSnap@83] - Reading snapshot f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test2237069409898274011.junit.dir\version-2\snapshot.b [junit] 2013-10-17 11:25:50,319 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test2237069409898274011.junit.dir\version-2\snapshot.b [junit] 2013-10-17 11:25:50,321 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-10-17 11:25:50,322 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:53980 [junit] 2013-10-17 11:25:50,419 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@828] - Processing stat command from /127.0.0.1:53980 [junit] 2013-10-17 11:25:50,419 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@677] - Stat command output [junit] 2013-10-17 11:25:50,420 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@999] - Closed socket connection for client /127.0.0.1:53980 (no session established for client) [junit] 2013-10-17 11:25:50,420 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-10-17 11:25:50,519 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-10-17 11:25:50,519 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-10-17 11:25:50,520 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-10-17 11:25:50,520 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-10-17 11:25:50,520 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2013-10-17 11:25:50,619 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-10-17 11:25:50,642 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@882] - Socket connection established to 127.0.0.1/127.0.0.1:11221, initiating session [junit] 2013-10-17 11:25:50,642 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:53975 [junit] 2013-10-17 11:25:50,643 [myid:] - INFO [NIOWorkerThread-2:ZooKeeperServer@858] - Client attempting to renew session 0x141c5f31e68 at /127.0.0.1:53975 [junit] 2013-10-17 11:25:50,719 [myid:] - INFO [NIOWorkerThread-2:ZooKeeperServer@604] - Established session 0x141c5f31e68 with negotiated timeout 3 for client /127.0.0.1:53975 [junit] 2013-10-17 11:25:50,720 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1261] - Session establishment complete on server 127.0.0.1/127.0.0.1:1
[jira] [Commented] (ZOOKEEPER-442) need a way to remove watches that are no longer of interest
[
https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797891#comment-13797891
]
Edward Ribeiro commented on ZOOKEEPER-442:
--
The offending javadoc warning in the latest patch:
[exec] [javadoc]
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java:2326:
warning - Tag @see: can't find removeWatches(String, Watcher, WatcherType,
boolean) in org.apache.zookeeper.ZooKeeper
The offending line seem to be this: @see #removeWatches(String, Watcher,
WatcherType, boolean)
Just a guess: wouldn't it be @see {@link #removeWatches(String, Watcher,
WatcherType, boolean)} ?
Edward
> need a way to remove watches that are no longer of interest
> ---
>
> Key: ZOOKEEPER-442
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442
> Project: ZooKeeper
> Issue Type: New Feature
>Reporter: Benjamin Reed
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.5.0
>
> Attachments: Remove Watch API.pdf, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch,
> ZOOKEEPER-442.patch, ZOOKEEPER-442.patch
>
>
> currently the only way a watch cleared is to trigger it. we need a way to
> enumerate the outstanding watch objects, find watch events the objects are
> watching for, and remove interests in an event.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
subscribe to the ZooKeeper developer mailing list
Hi,I would like to know something about ZooKeeper developing.I subscribe to the ZooKeeper developer mailing list for the infomation. Thank you.
Re: subscribe to the ZooKeeper developer mailing list
See http://zookeeper.apache.org/lists.html On Thu, Oct 17, 2013 at 5:59 AM, Hokkoo wrote: > Hi,I would like to know something about ZooKeeper developing.I subscribe > to the ZooKeeper developer mailing list for the infomation. > Thank you.
[jira] [Commented] (ZOOKEEPER-1646) mt c client tests fail on Ubuntu Raring
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798082#comment-13798082 ] Mahadev konar commented on ZOOKEEPER-1646: -- +1 for the patch. Nice catch Pat! > mt c client tests fail on Ubuntu Raring > --- > > Key: ZOOKEEPER-1646 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1646 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.4.5, 3.5.0 > Environment: Ubuntu 13.04 (raring), glibc 2.17 >Reporter: James Page >Assignee: Patrick Hunt >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1646.patch > > > Misc tests fail in the c client binding under the current Ubuntu development > release: > ./zktest-mt > ZooKeeper server startedRunning > Zookeeper_clientretry::testRetry ZooKeeper server started ZooKeeper server > started : elapsed 9315 : OK > Zookeeper_operations::testAsyncWatcher1 : assertion : elapsed 1054 > Zookeeper_operations::testAsyncGetOperation : assertion : elapsed 1055 > Zookeeper_operations::testOperationsAndDisconnectConcurrently1 : assertion : > elapsed 1066 > Zookeeper_operations::testOperationsAndDisconnectConcurrently2 : elapsed 0 : > OK > Zookeeper_operations::testConcurrentOperations1 : assertion : elapsed 1055 > Zookeeper_init::testBasic : elapsed 1 : OK > Zookeeper_init::testAddressResolution : elapsed 0 : OK > Zookeeper_init::testMultipleAddressResolution : elapsed 0 : OK > Zookeeper_init::testNullAddressString : elapsed 0 : OK > Zookeeper_init::testEmptyAddressString : elapsed 0 : OK > Zookeeper_init::testOneSpaceAddressString : elapsed 0 : OK > Zookeeper_init::testTwoSpacesAddressString : elapsed 0 : OK > Zookeeper_init::testInvalidAddressString1 : elapsed 0 : OK > Zookeeper_init::testInvalidAddressString2 : elapsed 175 : OK > Zookeeper_init::testNonexistentHost : elapsed 92 : OK > Zookeeper_init::testOutOfMemory_init : elapsed 0 : OK > Zookeeper_init::testOutOfMemory_getaddrs1 : elapsed 0 : OK > Zookeeper_init::testOutOfMemory_getaddrs2 : elapsed 1 : OK > Zookeeper_init::testPermuteAddrsList : elapsed 0 : OK > Zookeeper_close::testIOThreadStoppedOnExpire : assertion : elapsed 1056 > Zookeeper_close::testCloseUnconnected : elapsed 0 : OK > Zookeeper_close::testCloseUnconnected1 : elapsed 91 : OK > Zookeeper_close::testCloseConnected1 : assertion : elapsed 1056 > Zookeeper_close::testCloseFromWatcher1 : assertion : elapsed 1076 > Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server started : > elapsed 12155 : OK > Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK > Zookeeper_simpleSystem::testNullData : elapsed 1031 : OK > Zookeeper_simpleSystem::testIPV6 : elapsed 1005 : OK > Zookeeper_simpleSystem::testPath : elapsed 1024 : OK > Zookeeper_simpleSystem::testPathValidation : elapsed 1053 : OK > Zookeeper_simpleSystem::testPing : elapsed 17287 : OK > Zookeeper_simpleSystem::testAcl : elapsed 1019 : OK > Zookeeper_simpleSystem::testChroot : elapsed 3052 : OK > Zookeeper_simpleSystem::testAuth : assertion : elapsed 7010 > Zookeeper_simpleSystem::testHangingClient : elapsed 1015 : OK > Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper server > started ZooKeeper server started ZooKeeper server started : elapsed 20556 : OK > Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper server > started ZooKeeper server started ZooKeeper server started : elapsed 20563 : OK > Zookeeper_simpleSystem::testGetChildren2 : elapsed 1041 : OK > Zookeeper_multi::testCreate : elapsed 1017 : OK > Zookeeper_multi::testCreateDelete : elapsed 1007 : OK > Zookeeper_multi::testInvalidVersion : elapsed 1011 : OK > Zookeeper_multi::testNestedCreate : elapsed 1009 : OK > Zookeeper_multi::testSetData : elapsed 6019 : OK > Zookeeper_multi::testUpdateConflict : elapsed 1014 : OK > Zookeeper_multi::testDeleteUpdateConflict : elapsed 1007 : OK > Zookeeper_multi::testAsyncMulti : elapsed 2001 : OK > Zookeeper_multi::testMultiFail : elapsed 1006 : OK > Zookeeper_multi::testCheck : elapsed 1020 : OK > Zookeeper_multi::testWatch : elapsed 2013 : OK > Zookeeper_watchers::testDefaultSessionWatcher1zktest-mt: > tests/ZKMocks.cc:271: SyncedBoolCondition > DeliverWatchersWrapper::isDelivered() const: Assertion `i<1000' failed. > Aborted (core dumped) > It would appear that the zookeeper connection does not transition to > connected within the required time; I increased the time allowed but no > change. > Ubuntu raring has glibc 2.17; the test suite works fine on previous Ubuntu > releases and this is the only difference that stood out. > Interestingly the cli_mt worked just fine connecting to the same zookeeper > instance that the tests left lying around so I'm assuming this is a test > error rather tha
[jira] [Updated] (ZOOKEEPER-442) need a way to remove watches that are no longer of interest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-442: --- Attachment: ZOOKEEPER-442.patch > need a way to remove watches that are no longer of interest > --- > > Key: ZOOKEEPER-442 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442 > Project: ZooKeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Assignee: Rakesh R >Priority: Critical > Fix For: 3.5.0 > > Attachments: Remove Watch API.pdf, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch > > > currently the only way a watch cleared is to trigger it. we need a way to > enumerate the outstanding watch objects, find watch events the objects are > watching for, and remove interests in an event. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1742) "make check" doesn't work on macos
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798128#comment-13798128 ] Patrick Hunt commented on ZOOKEEPER-1742: - With ZOOKEEPER-1646 and ZOOKEEPER-1795 fixed the c client tests are passing for me on Ubuntu Raring on both branch-3.4 and trunk. > "make check" doesn't work on macos > -- > > Key: ZOOKEEPER-1742 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1742 > Project: ZooKeeper > Issue Type: Bug >Reporter: Flavio Junqueira >Assignee: Benjamin Reed > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1742.patch > > > There are two problems I have spotted when running "make check" with the C > client. First, it complains that the sleep call is not defined in two test > files: tests/ZooKeeperQuorumServer.cc and tests/TestReconfigServer.cc. > Including unistd.h works. The second problem is with linker options. It > complains that "--wrap" is not a valid. I'm not sure how to deal with this > one yet, since I'm not sure why we are using it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1430: Assignee: Giridharan Kesavan (was: Patrick Hunt) > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.4.4, 3.5.0 >Reporter: Patrick Hunt >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch, > ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). > In particular we need to ensure the following artifacts get published: > * zookeeper-3.x.y.jar > * zookeeper-3.x.y-sources.jar > * zookeeper-3.x.y-tests.jar > * zookeeper-3.x.y-javadoc.jar > In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream > users, such as Hadoop. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798133#comment-13798133 ] Patrick Hunt commented on ZOOKEEPER-1430: - [~gkesavan] any update on this? > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.4.4, 3.5.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch, > ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). > In particular we need to ensure the following artifacts get published: > * zookeeper-3.x.y.jar > * zookeeper-3.x.y-sources.jar > * zookeeper-3.x.y-tests.jar > * zookeeper-3.x.y-javadoc.jar > In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream > users, such as Hadoop. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-442) need a way to remove watches that are no longer of interest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798150#comment-13798150 ] Hadoop QA commented on ZOOKEEPER-442: - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12608969/ZOOKEEPER-442.patch against trunk revision 1532152. +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/1704//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1704//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1704//console This message is automatically generated. > need a way to remove watches that are no longer of interest > --- > > Key: ZOOKEEPER-442 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442 > Project: ZooKeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Assignee: Rakesh R >Priority: Critical > Fix For: 3.5.0 > > Attachments: Remove Watch API.pdf, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch > > > currently the only way a watch cleared is to trigger it. we need a way to > enumerate the outstanding watch objects, find watch events the objects are > watching for, and remove interests in an event. -- This message was sent by Atlassian JIRA (v6.1#6144)
Success: ZOOKEEPER-442 PreCommit Build #1704
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-442 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1704/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 297642 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/12608969/ZOOKEEPER-442.patch [exec] against trunk revision 1532152. [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/1704//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1704//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1704//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] 04415d71cbb8401fdef6e55fadd7db6ba1227466 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 37 minutes 15 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-442 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-442) need a way to remove watches that are no longer of interest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798159#comment-13798159 ] Rakesh R commented on ZOOKEEPER-442: [~eribeiro] I've just modified the patch and now it works fine. > need a way to remove watches that are no longer of interest > --- > > Key: ZOOKEEPER-442 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442 > Project: ZooKeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Assignee: Rakesh R >Priority: Critical > Fix For: 3.5.0 > > Attachments: Remove Watch API.pdf, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch > > > currently the only way a watch cleared is to trigger it. we need a way to > enumerate the outstanding watch objects, find watch events the objects are > watching for, and remove interests in an event. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1674) There is no need to clear & load the database across leader election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798219#comment-13798219 ] Akshay Chander commented on ZOOKEEPER-1674: --- I am working with Thawan on this feature. I'd appreciate comments and suggestions for the analysis done so far. Retaining the database across leader election should improve the recovery time after leader election. In order to support such a feature, the following changes will be required to ensure that the existing behavior is maintained. 1) Anything that has reached the PrepRequestProcessor should make it to the SyncRequestProcessor. Similarly, anything that has reached the commitProcessor should eventually reach the FinalRequestProcessor. To maintain this invariant: a) Currently, we drop the database and reload from disk (snapshot + txnlog). We can effectively mimic this behavior in one of two ways. i) We retain outstandingProposals and toBeApplied (in the case of leader) or pendingTxns (in the case of followers) across the leader election. We will apply the txns in these data structures to the data tree before calling getInitLastLoggedZxid in lookForLeader()). This will ensure that the lastSeenZxid sent by the participant during the leader election will remain the same as before this feature. ii) Alternatively, we could apply these txns to the data tree during the shutdown phase. This way, we dont need to do the extra work of persisting these data structures across leader elections. b) During shutdown, we should ensure that all appends to the txnlog have actually been flushed to the disk. c) By retaining the zkDataBase, we will also be retaining the sessionsWithTimeouts, which is a listing of global sessions. We need to ensure that this is now clean after the leader election. Leader: If there is an upgrade request for a session (from local to global), we add it to the global session tracker. Since this is going to persist across leader election, we need to ensure that the txn corresponding to this createSession is present in atleast the txnlog. Therefore we need to ensure that requests that are in the PrepRequestProcessor make their way to the SyncRequestProcessor even if there is a shutdown at any point in between. d) Ensure that anything in the FinalRequestProcessor gets applied to the Data Tree. 2) Don't take a dirty snapshot. We don't want txns that haven't been accepted by a majority of the quorum to be part of any snapshot. Currently, we take snapshots on shutdown and in loadData, which we will stop doing. 3) In followers, there is a bug in the local session code. When there is an upgrade request, we currently remove the session from the local session tracker and add it to globalSessionWithTimeouts in the local request processor itself (checkUpgradeSession) We probably should not add it to the global sessions just yet and let it be done in the final request processor. 4) Another small bug: In learnerSessionTracker::touchSession, currently if a session is not in the localSessionTracker and not a global session, then we return false. this should not be the case any longer. This is because we may have removed the session from the local session tracker for an upgrade request. So just add it to the touchTable and return true. This analysis was done on our internal branch which is based of 3.4. Therefore, we haven't investigated how this feature would be affected by the Dynamic Reconfiguration feature. > There is no need to clear & load the database across leader election > > > Key: ZOOKEEPER-1674 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1674 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Jacky007 > > It is interesting to notice the piece of codes in QuorumPeer.java > /* ZKDatabase is a top level member of quorumpeer > * which will be used in all the zookeeperservers > * instantiated later. Also, it is created once on > * bootup and only thrown away in case of a truncate > * message from the leader > */ > private ZKDatabase zkDb; > It is introduced by ZOOKEEPER-596. Now, we just drop the database every > leader election. > We can keep it safely with ZOOKEEPER-1549. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1607) Read-only Observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raul Gutierrez Segales updated ZOOKEEPER-1607: -- Attachment: (was: persistent-read-only-for-observers.patch) > Read-only Observer > -- > > Key: ZOOKEEPER-1607 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.3 >Reporter: Thawan Kooburat >Assignee: Raul Gutierrez Segales > Fix For: 3.5.0 > > > This feature reused some of the mechanism already provided by > ReadOnlyZooKeeper (ZOOKEEPER-704) but implemented in a different way > Goal: read-only clients should be able to connect to the observer or continue > to read data from the observer event when there is an outage of underling > quorum. This means that it is possible for the observer to provide 100% read > uptime for read-only local session (ZOOKEEPER-1147) > Implementation: > The observer don't tear down itself when it lose connection with the leader. > It only close the connection associated with non read-only sessions and > global sessions. So the client can try other observer if this is a temporal > failure. > During the outage, the observer switch to read-only mode. All the pending and > future write requests get will get NOT_READONLY error. Read-only state > transition is sent to all session on that observer. The observer only accepts > a new connection from a read-only client. > When the observer is able to reconnect to the leader. It sends state > transition (CONNECTED_STATE) to all current session. If it is able to > synchronize with the leader using DIFF, the steam of txns is sent through the > commit processor instead of applying to the DataTree directly to prevent > raise condition between in-flight read requests (see ZOOKEEPER-1505). The > client will receive watch events correctly and can start issuing write > requests. > However, if the observer is getting the snapshot. It need to drop all the > connection since it cannot fire a watch correctly. > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1607) Read-only Observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raul Gutierrez Segales updated ZOOKEEPER-1607: -- Attachment: ZOOKEEPER-1607.patch Chatted with Thawan about this and this still probably has to change but I wanted to go ahead and post this for any interested passerby (since local sessions support has been merged). > Read-only Observer > -- > > Key: ZOOKEEPER-1607 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.3 >Reporter: Thawan Kooburat >Assignee: Raul Gutierrez Segales > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1607.patch > > > This feature reused some of the mechanism already provided by > ReadOnlyZooKeeper (ZOOKEEPER-704) but implemented in a different way > Goal: read-only clients should be able to connect to the observer or continue > to read data from the observer event when there is an outage of underling > quorum. This means that it is possible for the observer to provide 100% read > uptime for read-only local session (ZOOKEEPER-1147) > Implementation: > The observer don't tear down itself when it lose connection with the leader. > It only close the connection associated with non read-only sessions and > global sessions. So the client can try other observer if this is a temporal > failure. > During the outage, the observer switch to read-only mode. All the pending and > future write requests get will get NOT_READONLY error. Read-only state > transition is sent to all session on that observer. The observer only accepts > a new connection from a read-only client. > When the observer is able to reconnect to the leader. It sends state > transition (CONNECTED_STATE) to all current session. If it is able to > synchronize with the leader using DIFF, the steam of txns is sent through the > commit processor instead of applying to the DataTree directly to prevent > raise condition between in-flight read requests (see ZOOKEEPER-1505). The > client will receive watch events correctly and can start issuing write > requests. > However, if the observer is getting the snapshot. It need to drop all the > connection since it cannot fire a watch correctly. > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1607) Read-only Observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798617#comment-13798617 ] Hadoop QA commented on ZOOKEEPER-1607: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12609061/ZOOKEEPER-1607.patch against trunk revision 1533161. +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 patch appears to cause tar ant target to fail. -1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail. +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/1705//testReport/ Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1705//console This message is automatically generated. > Read-only Observer > -- > > Key: ZOOKEEPER-1607 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.3 >Reporter: Thawan Kooburat >Assignee: Raul Gutierrez Segales > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1607.patch > > > This feature reused some of the mechanism already provided by > ReadOnlyZooKeeper (ZOOKEEPER-704) but implemented in a different way > Goal: read-only clients should be able to connect to the observer or continue > to read data from the observer event when there is an outage of underling > quorum. This means that it is possible for the observer to provide 100% read > uptime for read-only local session (ZOOKEEPER-1147) > Implementation: > The observer don't tear down itself when it lose connection with the leader. > It only close the connection associated with non read-only sessions and > global sessions. So the client can try other observer if this is a temporal > failure. > During the outage, the observer switch to read-only mode. All the pending and > future write requests get will get NOT_READONLY error. Read-only state > transition is sent to all session on that observer. The observer only accepts > a new connection from a read-only client. > When the observer is able to reconnect to the leader. It sends state > transition (CONNECTED_STATE) to all current session. If it is able to > synchronize with the leader using DIFF, the steam of txns is sent through the > commit processor instead of applying to the DataTree directly to prevent > raise condition between in-flight read requests (see ZOOKEEPER-1505). The > client will receive watch events correctly and can start issuing write > requests. > However, if the observer is getting the snapshot. It need to drop all the > connection since it cannot fire a watch correctly. > -- This message was sent by Atlassian JIRA (v6.1#6144)
Failed: ZOOKEEPER-1607 PreCommit Build #1705
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1705/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 479 lines...] [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12609061/ZOOKEEPER-1607.patch [exec] against trunk revision 1533161. [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 patch appears to cause tar ant target to fail. [exec] [exec] -1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail. [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/1705//testReport/ [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1705//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] 0ce11f664164205b93c73281d3f6a2b048939d10 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: 3 Total time: 1 minute 29 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1607 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Updated] (ZOOKEEPER-1607) Read-only Observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raul Gutierrez Segales updated ZOOKEEPER-1607: -- Attachment: (was: ZOOKEEPER-1607.patch) > Read-only Observer > -- > > Key: ZOOKEEPER-1607 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.3 >Reporter: Thawan Kooburat >Assignee: Raul Gutierrez Segales > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1607.patch > > > This feature reused some of the mechanism already provided by > ReadOnlyZooKeeper (ZOOKEEPER-704) but implemented in a different way > Goal: read-only clients should be able to connect to the observer or continue > to read data from the observer event when there is an outage of underling > quorum. This means that it is possible for the observer to provide 100% read > uptime for read-only local session (ZOOKEEPER-1147) > Implementation: > The observer don't tear down itself when it lose connection with the leader. > It only close the connection associated with non read-only sessions and > global sessions. So the client can try other observer if this is a temporal > failure. > During the outage, the observer switch to read-only mode. All the pending and > future write requests get will get NOT_READONLY error. Read-only state > transition is sent to all session on that observer. The observer only accepts > a new connection from a read-only client. > When the observer is able to reconnect to the leader. It sends state > transition (CONNECTED_STATE) to all current session. If it is able to > synchronize with the leader using DIFF, the steam of txns is sent through the > commit processor instead of applying to the DataTree directly to prevent > raise condition between in-flight read requests (see ZOOKEEPER-1505). The > client will receive watch events correctly and can start issuing write > requests. > However, if the observer is getting the snapshot. It need to drop all the > connection since it cannot fire a watch correctly. > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1607) Read-only Observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raul Gutierrez Segales updated ZOOKEEPER-1607: -- Attachment: ZOOKEEPER-1607.patch The prev patch had remaining bits and pieces of an internal patch to keep stats using Twitter's stats-util - soz. > Read-only Observer > -- > > Key: ZOOKEEPER-1607 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.3 >Reporter: Thawan Kooburat >Assignee: Raul Gutierrez Segales > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1607.patch > > > This feature reused some of the mechanism already provided by > ReadOnlyZooKeeper (ZOOKEEPER-704) but implemented in a different way > Goal: read-only clients should be able to connect to the observer or continue > to read data from the observer event when there is an outage of underling > quorum. This means that it is possible for the observer to provide 100% read > uptime for read-only local session (ZOOKEEPER-1147) > Implementation: > The observer don't tear down itself when it lose connection with the leader. > It only close the connection associated with non read-only sessions and > global sessions. So the client can try other observer if this is a temporal > failure. > During the outage, the observer switch to read-only mode. All the pending and > future write requests get will get NOT_READONLY error. Read-only state > transition is sent to all session on that observer. The observer only accepts > a new connection from a read-only client. > When the observer is able to reconnect to the leader. It sends state > transition (CONNECTED_STATE) to all current session. If it is able to > synchronize with the leader using DIFF, the steam of txns is sent through the > commit processor instead of applying to the DataTree directly to prevent > raise condition between in-flight read requests (see ZOOKEEPER-1505). The > client will receive watch events correctly and can start issuing write > requests. > However, if the observer is getting the snapshot. It need to drop all the > connection since it cannot fire a watch correctly. > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1607) Read-only Observer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798677#comment-13798677 ] Hadoop QA commented on ZOOKEEPER-1607: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12609067/ZOOKEEPER-1607.patch against trunk revision 1533161. +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 appears to introduce 1 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 failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1706//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1706//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1706//console This message is automatically generated. > Read-only Observer > -- > > Key: ZOOKEEPER-1607 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.3 >Reporter: Thawan Kooburat >Assignee: Raul Gutierrez Segales > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1607.patch > > > This feature reused some of the mechanism already provided by > ReadOnlyZooKeeper (ZOOKEEPER-704) but implemented in a different way > Goal: read-only clients should be able to connect to the observer or continue > to read data from the observer event when there is an outage of underling > quorum. This means that it is possible for the observer to provide 100% read > uptime for read-only local session (ZOOKEEPER-1147) > Implementation: > The observer don't tear down itself when it lose connection with the leader. > It only close the connection associated with non read-only sessions and > global sessions. So the client can try other observer if this is a temporal > failure. > During the outage, the observer switch to read-only mode. All the pending and > future write requests get will get NOT_READONLY error. Read-only state > transition is sent to all session on that observer. The observer only accepts > a new connection from a read-only client. > When the observer is able to reconnect to the leader. It sends state > transition (CONNECTED_STATE) to all current session. If it is able to > synchronize with the leader using DIFF, the steam of txns is sent through the > commit processor instead of applying to the DataTree directly to prevent > raise condition between in-flight read requests (see ZOOKEEPER-1505). The > client will receive watch events correctly and can start issuing write > requests. > However, if the observer is getting the snapshot. It need to drop all the > connection since it cannot fire a watch correctly. > -- This message was sent by Atlassian JIRA (v6.1#6144)
Failed: ZOOKEEPER-1607 PreCommit Build #1706
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1607 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1706/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 311589 lines...] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12609067/ZOOKEEPER-1607.patch [exec] against trunk revision 1533161. [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 appears to introduce 1 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 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/1706//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1706//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1706//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] 18e542d9b211fbe7710562b63322cba806487859 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: 2 Total time: 39 minutes 13 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1607 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 1 tests failed. REGRESSION: org.apache.zookeeper.test.ReconfigTest.testQuorumSystemChange 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-442) need a way to remove watches that are no longer of interest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798800#comment-13798800 ] Rakesh R commented on ZOOKEEPER-442: I'd appreciate any suggestions or comments about the fix and test cases. Thanks > need a way to remove watches that are no longer of interest > --- > > Key: ZOOKEEPER-442 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-442 > Project: ZooKeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Assignee: Rakesh R >Priority: Critical > Fix For: 3.5.0 > > Attachments: Remove Watch API.pdf, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, > ZOOKEEPER-442.patch, ZOOKEEPER-442.patch, ZOOKEEPER-442.patch > > > currently the only way a watch cleared is to trigger it. we need a way to > enumerate the outstanding watch objects, find watch events the objects are > watching for, and remove interests in an event. -- This message was sent by Atlassian JIRA (v6.1#6144)
