ZooKeeper_branch34_solaris - Build # 15 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/15/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 137322 lines...] [junit] 2011-11-09 08:09:32,307 [myid:] - INFO [Thread-4:NIOServerCnxn@1000] - Closed socket connection for client /127.0.0.1:54248 (no session established for client) [junit] 2011-11-09 08:09:32,307 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2011-11-09 08:09:32,308 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2011-11-09 08:09:32,309 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2011-11-09 08:09:32,309 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2011-11-09 08:09:32,310 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2011-11-09 08:09:32,310 [myid:] - INFO [main:ClientBase@435] - STOPPING server [junit] 2011-11-09 08:09:32,311 [myid:] - INFO [main:ZooKeeperServer@420] - shutting down [junit] 2011-11-09 08:09:32,312 [myid:] - INFO [main:SessionTrackerImpl@206] - Shutting down [junit] 2011-11-09 08:09:32,312 [myid:] - INFO [main:PrepRequestProcessor@730] - Shutting down [junit] 2011-11-09 08:09:32,313 [myid:] - INFO [main:SyncRequestProcessor@173] - Shutting down [junit] 2011-11-09 08:09:32,313 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@135] - PrepRequestProcessor exited loop! [junit] 2011-11-09 08:09:32,314 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@155] - SyncRequestProcessor exited! [junit] 2011-11-09 08:09:32,314 [myid:] - INFO [main:FinalRequestProcessor@423] - shutdown of request processor complete [junit] 2011-11-09 08:09:32,315 [myid:] - INFO [main:ClientBase@227] - connecting to 127.0.0.1 11221 [junit] 2011-11-09 08:09:32,316 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2011-11-09 08:09:32,317 [myid:] - INFO [main:ClientBase@428] - STARTING server [junit] 2011-11-09 08:09:32,318 [myid:] - INFO [main:ZooKeeperServer@168] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test6118196529391521492.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test6118196529391521492.junit.dir/version-2 [junit] 2011-11-09 08:09:32,319 [myid:] - INFO [main:NIOServerCnxnFactory@110] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2011-11-09 08:09:32,320 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test6118196529391521492.junit.dir/version-2/snapshot.b [junit] 2011-11-09 08:09:32,322 [myid:] - INFO [main:FileTxnSnapLog@255] - Snapshotting: b [junit] 2011-11-09 08:09:32,324 [myid:] - INFO [main:ClientBase@227] - connecting to 127.0.0.1 11221 [junit] 2011-11-09 08:09:32,325 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@213] - Accepted socket connection from /127.0.0.1:54250 [junit] 2011-11-09 08:09:32,326 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@820] - Processing stat command from /127.0.0.1:54250 [junit] 2011-11-09 08:09:32,327 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@655] - Stat command output [junit] 2011-11-09 08:09:32,327 [myid:] - INFO [Thread-5:NIOServerCnxn@1000] - Closed socket connection for client /127.0.0.1:54250 (no session established for client) [junit] 2011-11-09 08:09:32,328 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2011-11-09 08:09:32,329 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2011-11-09 08:09:32,330 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2011-11-09 08:09:32,330 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2011-11-09 08:09:32,331 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2011-11-09 08:09:32,331 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2011-11-09 08:09:32,332 [myid:] - INFO [main:ClientBase@465] - tearDown starting [junit] 2011-11-09 08:09:32,400 [myid:] - INFO [main:ZooKeeper@679] - Session: 0x133875ff30f closed
ZooKeeper-trunk-jdk7 - Build # 81 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-jdk7/81/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 144463 lines...] [junit] 2011-11-09 09:51:34,911 [myid:] - INFO [main:ClientBase@435] - STOPPING server [junit] 2011-11-09 09:51:34,911 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@240] - NIOServerCnxn factory exited run method [junit] 2011-11-09 09:51:34,911 [myid:] - INFO [main:ZooKeeperServer@391] - shutting down [junit] 2011-11-09 09:51:34,911 [myid:] - INFO [main:SessionTrackerImpl@206] - Shutting down [junit] 2011-11-09 09:51:34,911 [myid:] - INFO [main:PrepRequestProcessor@694] - Shutting down [junit] 2011-11-09 09:51:34,912 [myid:] - INFO [main:SyncRequestProcessor@173] - Shutting down [junit] 2011-11-09 09:51:34,912 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@134] - PrepRequestProcessor exited loop! [junit] 2011-11-09 09:51:34,912 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@155] - SyncRequestProcessor exited! [junit] 2011-11-09 09:51:34,912 [myid:] - INFO [main:FinalRequestProcessor@419] - shutdown of request processor complete [junit] 2011-11-09 09:51:34,912 [myid:] - INFO [main:ClientBase@227] - connecting to 127.0.0.1 11221 [junit] 2011-11-09 09:51:34,913 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2011-11-09 09:51:34,914 [myid:] - INFO [main:ClientBase@428] - STARTING server [junit] 2011-11-09 09:51:34,914 [myid:] - INFO [main:ZooKeeperServer@143] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test6860516864306346944.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test6860516864306346944.junit.dir/version-2 [junit] 2011-11-09 09:51:34,915 [myid:] - INFO [main:NIOServerCnxnFactory@110] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2011-11-09 09:51:34,915 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test6860516864306346944.junit.dir/version-2/snapshot.b [junit] 2011-11-09 09:51:34,917 [myid:] - INFO [main:FileTxnSnapLog@255] - Snapshotting: b [junit] 2011-11-09 09:51:34,919 [myid:] - INFO [main:ClientBase@227] - connecting to 127.0.0.1 11221 [junit] 2011-11-09 09:51:34,919 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@213] - Accepted socket connection from /127.0.0.1:41508 [junit] 2011-11-09 09:51:34,919 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@820] - Processing stat command from /127.0.0.1:41508 [junit] 2011-11-09 09:51:34,920 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@655] - Stat command output [junit] 2011-11-09 09:51:34,920 [myid:] - INFO [Thread-4:NIOServerCnxn@1000] - Closed socket connection for client /127.0.0.1:41508 (no session established for client) [junit] 2011-11-09 09:51:34,920 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2011-11-09 09:51:34,922 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2011-11-09 09:51:34,922 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2011-11-09 09:51:34,922 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2011-11-09 09:51:34,922 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2011-11-09 09:51:34,922 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2011-11-09 09:51:34,923 [myid:] - INFO [main:ClientBase@465] - tearDown starting [junit] 2011-11-09 09:51:34,997 [myid:] - INFO [main:ZooKeeper@679] - Session: 0x13387bd5f33 closed [junit] 2011-11-09 09:51:34,998 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@511] - EventThread shut down [junit] 2011-11-09 09:51:34,998 [myid:] - INFO [main:ClientBase@435] - STOPPING server [junit] 2011-11-09 09:51:34,998 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@240] - NIOServerCnxn factory exited run method [junit] 2011-11-09 09:51:34,998 [myid:] - INFO [main:ZooKeeperServer@391] - shutting down [junit] 2011-11-09 09:51:34,999 [myid:] - INFO [main:SessionTrackerImpl@206] - Shutting down [junit] 2011-11-09 09:51:34,999 [myid:] - INFO [main:PrepRequestProcessor@694] - Shutting down [junit] 2011-11-09 09:51:34,999 [myid:] - INFO [main:SyncRequestProcessor@173] - Shutting
[jira] [Created] (ZOOKEEPER-1294) One of the zookeeper server is not accepting any requests
One of the zookeeper server is not accepting any requests - Key: ZOOKEEPER-1294 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1294 Project: ZooKeeper Issue Type: Bug Components: server Environment: 3 Zookeeper + 3 Observer with SuSe-11 Reporter: amith In zoo.cfg i have configured as server.1 = XX.XX.XX.XX:65175:65173 server.2 = XX.XX.XX.XX:65185:65183 server.3 = XX.XX.XX.XX:65195:65193 server.4 = XX.XX.XX.XX:65205:65203:observer server.5 = XX.XX.XX.XX:65215:65213:observer server.6 = XX.XX.XX.XX:65225:65223:observer Like above I have configured 3 PARTICIPANTS and 3 OBSERVERS in the cluster of 6 zookeepers Steps to reproduce the defect 1. Start all the 3 participant zookeeper 2. Stop all the participant zookeeper 3. Start zookeeper 1(Participant) 4. Start zookeeper 2(Participant) 5. Start zookeeper 4(Observer) 6. Create a persistent node with external client and close it 7. Stop the zookeeper 1(Participant neo quorum is unstable) 8. Create a new client and try to find the node created b4 using exists api (will fail since quorum not statisfied) 9. Start the Zookeeper 1 (Participant stabilise the quorum) Now check the observer using 4 letter word (Server.4) linux-216:/home/amith/CI/source/install/zookeeper/zookeeper2/bin # echo stat | netcat localhost 65200 Zookeeper version: 3.3.2-1031432, built on 11/05/2010 05:32 GMT Clients: /127.0.0.1:46370[0](queued=0,recved=1,sent=0) Latency min/avg/max: 0/0/0 Received: 1 Sent: 0 Outstanding: 0 Zxid: 0x10003 Mode: observer Node count: 5 check the participant 2 with 4 letter word Latency min/avg/max: 22/48/83 Received: 39 Sent: 3 Outstanding: 35 Zxid: 0x10003 Mode: leader Node count: 5 linux-216:/home/amith/CI/source/install/zookeeper/zookeeper2/bin # check the participant 1 with 4 letter word linux-216:/home/amith/CI/source/install/zookeeper/zookeeper2/bin # echo stat | netcat localhost 65170 This ZooKeeper instance is not currently serving requests We can see the participant1 logs filled with 2011-11-08 15:49:51,360 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:65170:NIOServerCnxn@642] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running Problem here is participent1 is not responding / accepting any requests -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (ZOOKEEPER-1294) One of the zookeeper server is not accepting any requests
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kavita sharma reassigned ZOOKEEPER-1294: Assignee: kavita sharma One of the zookeeper server is not accepting any requests - Key: ZOOKEEPER-1294 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1294 Project: ZooKeeper Issue Type: Bug Components: server Environment: 3 Zookeeper + 3 Observer with SuSe-11 Reporter: amith Assignee: kavita sharma In zoo.cfg i have configured as server.1 = XX.XX.XX.XX:65175:65173 server.2 = XX.XX.XX.XX:65185:65183 server.3 = XX.XX.XX.XX:65195:65193 server.4 = XX.XX.XX.XX:65205:65203:observer server.5 = XX.XX.XX.XX:65215:65213:observer server.6 = XX.XX.XX.XX:65225:65223:observer Like above I have configured 3 PARTICIPANTS and 3 OBSERVERS in the cluster of 6 zookeepers Steps to reproduce the defect 1. Start all the 3 participant zookeeper 2. Stop all the participant zookeeper 3. Start zookeeper 1(Participant) 4. Start zookeeper 2(Participant) 5. Start zookeeper 4(Observer) 6. Create a persistent node with external client and close it 7. Stop the zookeeper 1(Participant neo quorum is unstable) 8. Create a new client and try to find the node created b4 using exists api (will fail since quorum not statisfied) 9. Start the Zookeeper 1 (Participant stabilise the quorum) Now check the observer using 4 letter word (Server.4) linux-216:/home/amith/CI/source/install/zookeeper/zookeeper2/bin # echo stat | netcat localhost 65200 Zookeeper version: 3.3.2-1031432, built on 11/05/2010 05:32 GMT Clients: /127.0.0.1:46370[0](queued=0,recved=1,sent=0) Latency min/avg/max: 0/0/0 Received: 1 Sent: 0 Outstanding: 0 Zxid: 0x10003 Mode: observer Node count: 5 check the participant 2 with 4 letter word Latency min/avg/max: 22/48/83 Received: 39 Sent: 3 Outstanding: 35 Zxid: 0x10003 Mode: leader Node count: 5 linux-216:/home/amith/CI/source/install/zookeeper/zookeeper2/bin # check the participant 1 with 4 letter word linux-216:/home/amith/CI/source/install/zookeeper/zookeeper2/bin # echo stat | netcat localhost 65170 This ZooKeeper instance is not currently serving requests We can see the participant1 logs filled with 2011-11-08 15:49:51,360 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:65170:NIOServerCnxn@642] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running Problem here is participent1 is not responding / accepting any requests -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1292) FLETest is flaky
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated ZOOKEEPER-1292: Attachment: ZOOKEEPER-1292.patch I have rewritten the testLE case. With this patch, I have a new, simpler version of LEThread and have made it in such a way that it enables us to shutdown a number of leaders, forcing a new election. The different test cases refer to the number of leaders we shut down. FLETest is flaky Key: ZOOKEEPER-1292 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1292 Project: ZooKeeper Issue Type: Improvement Components: leaderElection Reporter: Flavio Junqueira Assignee: Flavio Junqueira Fix For: 3.5.0 Attachments: ZOOKEEPER-1292.patch, ZOOKEEPER-1292.patch testLE in FLETest is convoluted, difficult to read, and doesn't test FLE appropriately. The goal of this jira is to clean it up and propose a more reasonable test case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Success: ZOOKEEPER-1292 PreCommit Build #783
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1292 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/783/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 145736 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/12503081/ZOOKEEPER-1292.patch [exec] against trunk revision 1198053. [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/783//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/783//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/783//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] e91NCDHsv9 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 24 minutes 4 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1292 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-1292) FLETest is flaky
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13147068#comment-13147068 ] Hadoop QA commented on ZOOKEEPER-1292: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12503081/ZOOKEEPER-1292.patch against trunk revision 1198053. +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/783//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/783//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/783//console This message is automatically generated. FLETest is flaky Key: ZOOKEEPER-1292 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1292 Project: ZooKeeper Issue Type: Improvement Components: leaderElection Reporter: Flavio Junqueira Assignee: Flavio Junqueira Fix For: 3.5.0 Attachments: ZOOKEEPER-1292.patch, ZOOKEEPER-1292.patch testLE in FLETest is convoluted, difficult to read, and doesn't test FLE appropriately. The goal of this jira is to clean it up and propose a more reasonable test case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ZOOKEEPER-1295) Documentation for jute.maxbuffer is not correct in ZooKeeper Administrator's Guide
Documentation for jute.maxbuffer is not correct in ZooKeeper Administrator's
Guide
--
Key: ZOOKEEPER-1295
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1295
Project: ZooKeeper
Issue Type: Bug
Components: documentation
Affects Versions: 3.3.2
Reporter: Daniel Lord
The jute maxbuffer size is documented as being defaulted to 1 megabyte in the
administrators guide. I believe that this is true server side but it is not
true client side. On the client side the default is (at least in 3.3.2) this:
packetLen = Integer.getInteger(jute.maxbuffer, 4096 * 1024);
On the server side the documentation looks to be correct:
private static int determineMaxBuffer() {
String maxBufferString = System.getProperty(jute.maxbuffer);
try {
return Integer.parseInt(maxBufferString);
} catch(Exception e) {
return 0xf;
}
}
The documentation states this:
jute.maxbuffer:
(Java system property: jute.maxbuffer)
This option can only be set as a Java system property. There is no zookeeper
prefix on it. It specifies the maximum size of the data that can be stored in a
znode. The default is 0xf, or just under 1M. If this option is changed, the
system property must be set on all servers and clients otherwise problems will
arise. This is really a sanity check. ZooKeeper is designed to store data on
the order of kilobytes in size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ZOOKEEPER-1296) Add zookeeper-setup-conf.sh script
Add zookeeper-setup-conf.sh script
--
Key: ZOOKEEPER-1296
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1296
Project: ZooKeeper
Issue Type: Improvement
Components: scripts
Affects Versions: 3.4.0
Environment: Shell script
Reporter: Eric Yang
Assignee: Eric Yang
Priority: Minor
It would be nice to provide a setup script for zoo.cfg and zookeeper-env.sh.
The proposed script will provide the following options:
{noformat}
usage: /usr/sbin/zookeeper-setup-conf.sh parameters
Required parameters:
--conf-dir Set ZooKeeper configuration directory
--log-dir Set ZooKeeper log directory
Optional parameters:
--auto-purge-interval=1Set snapshot auto purge interval
--client-port=2181 Set client port
--data-dir=/var/lib/zookeeper Set data directory
--hosts=host1,host2Set ZooKeeper qourum hostnames
--init-limit=10Set initial sync limit
--java-homeSet JAVA_HOME location
--snapshot-count=3 Set snapshot retain count
--sync-limit=5 Set sync limit
--tick-time=2000 Set milliseconds of each tick
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1296) Add zookeeper-setup-conf.sh script
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated ZOOKEEPER-1296:
-
Attachment: ZOOKEEPER-1296.patch
ZooKeeper setup script.
Add zookeeper-setup-conf.sh script
--
Key: ZOOKEEPER-1296
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1296
Project: ZooKeeper
Issue Type: Improvement
Components: scripts
Affects Versions: 3.4.0
Environment: Shell script
Reporter: Eric Yang
Assignee: Eric Yang
Priority: Minor
Attachments: ZOOKEEPER-1296.patch
It would be nice to provide a setup script for zoo.cfg and zookeeper-env.sh.
The proposed script will provide the following options:
{noformat}
usage: /usr/sbin/zookeeper-setup-conf.sh parameters
Required parameters:
--conf-dir Set ZooKeeper configuration directory
--log-dir Set ZooKeeper log directory
Optional parameters:
--auto-purge-interval=1Set snapshot auto purge interval
--client-port=2181 Set client port
--data-dir=/var/lib/zookeeper Set data directory
--hosts=host1,host2Set ZooKeeper qourum hostnames
--init-limit=10Set initial sync limit
--java-homeSet JAVA_HOME location
--snapshot-count=3 Set snapshot retain count
--sync-limit=5 Set sync limit
--tick-time=2000 Set milliseconds of each tick
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1296) Add zookeeper-setup-conf.sh script
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13147356#comment-13147356
]
Hadoop QA commented on ZOOKEEPER-1296:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12503140/ZOOKEEPER-1296.patch
against trunk revision 1198053.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/784//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/784//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/784//console
This message is automatically generated.
Add zookeeper-setup-conf.sh script
--
Key: ZOOKEEPER-1296
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1296
Project: ZooKeeper
Issue Type: Improvement
Components: scripts
Affects Versions: 3.4.0
Environment: Shell script
Reporter: Eric Yang
Assignee: Eric Yang
Priority: Minor
Attachments: ZOOKEEPER-1296.patch
It would be nice to provide a setup script for zoo.cfg and zookeeper-env.sh.
The proposed script will provide the following options:
{noformat}
usage: /usr/sbin/zookeeper-setup-conf.sh parameters
Required parameters:
--conf-dir Set ZooKeeper configuration directory
--log-dir Set ZooKeeper log directory
Optional parameters:
--auto-purge-interval=1Set snapshot auto purge interval
--client-port=2181 Set client port
--data-dir=/var/lib/zookeeper Set data directory
--hosts=host1,host2Set ZooKeeper qourum hostnames
--init-limit=10Set initial sync limit
--java-homeSet JAVA_HOME location
--snapshot-count=3 Set snapshot retain count
--sync-limit=5 Set sync limit
--tick-time=2000 Set milliseconds of each tick
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Failed: ZOOKEEPER-1296 PreCommit Build #784
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1296 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/784/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 141390 lines...] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12503140/ZOOKEEPER-1296.patch [exec] against trunk revision 1198053. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/784//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/784//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/784//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] W1081v9DYA 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:1576: exec returned: 1 Total time: 23 minutes 41 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1296 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (BOOKKEEPER-101) Add Fencing to Bookkeeper
[ https://issues.apache.org/jira/browse/BOOKKEEPER-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13146882#comment-13146882 ] jirapos...@reviews.apache.org commented on BOOKKEEPER-101: -- bq. On 2011-11-08 23:15:23, fpj wrote: bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/Bookie.java, line 590 bq. https://reviews.apache.org/r/2594/diff/2/?file=56350#file56350line590 bq. bq. Ivan, just to confirm, the readEntry you say should have hit the bookie first is the one that reads the last confirmed? Yes, its the readEntry from LedgerRecoveryOp#initiate - Ivan --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2594/#review3120 --- On 2011-11-04 17:40:53, Ivan Kelly wrote: bq. bq. --- bq. This is an automatically generated e-mail. To reply, visit: bq. https://reviews.apache.org/r/2594/ bq. --- bq. bq. (Updated 2011-11-04 17:40:53) bq. bq. bq. Review request for bookkeeper. bq. bq. bq. Summary bq. --- bq. bq. BookKeeper is designed for use as a Write ahead log. In systems with a primary/backup architecture, the primary will write state updates to the WAL. If the primary dies the backup comes online, reads the WAL to get the latest state and starts serving requests. However, if the primary was only partitioned from the network, or stuck in a long GC, a split brain occurs. Both primary and backup can service client requests. bq. bq. Fencing(http://en.wikipedia.org/wiki/Fencing_%28computing%29) ensures that this cannot happen. With fencing, the backup can close the WAL of the primary, and cause any subsequent attempt by the primary to write to the WAL to give an error. bq. bq. bq. This addresses bug BOOKKEEPER-101. bq. https://issues.apache.org/jira/browse/BOOKKEEPER-101 bq. bq. bq. Diffs bq. - bq. bq.bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/Bookie.java d651894 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/BookieException.java 292617e bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/LedgerDescriptor.java 024cac3 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BKException.java d7c8f67 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BookKeeper.java a1fbab7 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BookKeeperAdmin.java b3eb5b9 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerCreateOp.java 6f72e47 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerHandle.java 8c2a54f bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerMetadata.java 328c7ca bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerOpenOp.java a68856c bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerRecoveryOp.java 7465c52 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingAddOp.java eddd760 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingReadOp.java 385b16c bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/client/ReadLastConfirmedOp.java c2d4cee bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieClient.java d70ae27 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieProtocol.java 873dafe bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieServer.java f1b3ad9 bq. bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/PerChannelBookieClient.java 2cd4de8 bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/client/LedgerCacheTest.java 07639aa bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/client/TestFencing.java PRE-CREATION bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/proto/TestProtoVersions.java f6cd8c9 bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/test/BaseTestCase.java 6bac569 bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/test/BookieClientTest.java 97dc2ab bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/test/BookieRecoveryTest.java ac54d9a bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/test/ConcurrentLedgerTest.java ebb17d2 bq. bookkeeper-server/src/test/java/org/apache/bookkeeper/test/LoopbackClient.java 85822bf bq. hedwig-server/src/main/java/org/apache/hedwig/server/benchmark/BookieBenchmark.java 18319d7 bq. bq. Diff: https://reviews.apache.org/r/2594/diff bq. bq. bq. Testing bq. --- bq. bq. bq. Thanks, bq. bq. Ivan
[jira] [Updated] (BOOKKEEPER-69) ServerRedirectLoopException when a machine (hosts bookie server hub server) reboot, which is caused by race condition of topic manager
[ https://issues.apache.org/jira/browse/BOOKKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-69: - Attachment: BOOKKEEPER-69.possiblefix.diff ServerRedirectLoopException when a machine (hosts bookie server hub server) reboot, which is caused by race condition of topic manager Key: BOOKKEEPER-69 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-69 Project: Bookkeeper Issue Type: Bug Components: hedwig-client, hedwig-server Affects Versions: 3.4.0 Environment: 3 machines (perf8, perf9, perf10), each machine hosts a bookie server a hub server. perf8 is used as default server for client 1. perf9 is used as default server for client 2. bookkeeper is configured as below: ensemble size is 3, quorum size is 2. Reporter: Sijie Guo Assignee: Sijie Guo Priority: Critical Fix For: 4.0.0 Attachments: BOOKKEEPER-69.possiblefix.diff, bookkeeper-69-testcase.patch, bookkeeper-69.patch, bookkeeper-69.patch 1) machine perf10 is rebooted. the bookie server hub server are not restarted automatically after reboot. 2) client 1 client 2 are still running. the topics owned in perf10 will be re-assigned to perf8/perf9. but they would fail because not enough bookie servers are available. 3) after 2 hours, we found that perf10 is rebooted. we restarted bookie server hub server on perf10 4) then we got ServerRedirectLoopException in client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (BOOKKEEPER-20) Hedwig Tests fail on trunk
[ https://issues.apache.org/jira/browse/BOOKKEEPER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly resolved BOOKKEEPER-20. -- Resolution: Duplicate Assignee: Ivan Kelly Fixed by BOOKKEEPER-102 Hedwig Tests fail on trunk -- Key: BOOKKEEPER-20 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-20 Project: Bookkeeper Issue Type: Bug Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Critical Fix For: 4.0.0 Results : Failed tests: testNonEmptyDirtyLedger(org.apache.hedwig.server.persistence.TestBookkeeperPersistenceManagerWhiteBox) testBasics(org.apache.hedwig.server.subscriptions.TestZkSubscriptionManager) testGetOwnerSingle(org.apache.hedwig.server.topics.TestZkTopicManager) testGetOwnerMulti(org.apache.hedwig.server.topics.TestZkTopicManager) testLoadBalancing(org.apache.hedwig.server.topics.TestZkTopicManager) testOwnershipChange(org.apache.hedwig.server.topics.TestZkTopicManager) testZKClientDisconnected(org.apache.hedwig.server.topics.TestZkTopicManager) testCreateFullPathOptimistic(org.apache.hedwig.zookeeper.TestZkUtils) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
