jzab slides
Hi, Here are the jzab slides from today's meetup. http://www.slideshare.net/easonliao315/zk-meetup-talk-41241692
[jira] [Commented] (ZOOKEEPER-1660) Add documentation for dynamic reconfiguration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201677#comment-14201677 ] Alexander Shraer commented on ZOOKEEPER-1660: - Here is a presentation I gave today in ZooKeeper meetup, based on the user manual: https://docs.google.com/presentation/d/1gtRUNaOzcnK4WfSY6bT8EyCf4iqrlHWWNxdqwAnPBow > Add documentation for dynamic reconfiguration > - > > Key: ZOOKEEPER-1660 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1660 > Project: ZooKeeper > Issue Type: Sub-task > Components: documentation >Affects Versions: 3.5.0 >Reporter: Alexander Shraer >Assignee: Reed Wanderman-Milne >Priority: Blocker > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-1660-v2.patch, ZOOKEEPER-1660-v3.patch, > ZOOKEEPER-1660.patch > > > Update user manual with reconfiguration info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1660) Add documentation for dynamic reconfiguration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201676#comment-14201676 ] Alexander Shraer commented on ZOOKEEPER-1660: - I committed the html and pdf to trunk. So I'm guessing they will become available in 3.5.1 > Add documentation for dynamic reconfiguration > - > > Key: ZOOKEEPER-1660 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1660 > Project: ZooKeeper > Issue Type: Sub-task > Components: documentation >Affects Versions: 3.5.0 >Reporter: Alexander Shraer >Assignee: Reed Wanderman-Milne >Priority: Blocker > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-1660-v2.patch, ZOOKEEPER-1660-v3.patch, > ZOOKEEPER-1660.patch > > > Update user manual with reconfiguration info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2071) Update docs for Apache branding and trademark requirements
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201358#comment-14201358 ] Wendy Smoak commented on ZOOKEEPER-2071: I'm not in love with the TM marks on every single page. At the time I was trying to follow The Rules as I interpreted them... but that part is a 'should' rather than 'must' anyway. My main concern was that I downloaded the 3.5.0-alpha .tar.gz distribution, and there was virtually no indication that it came from Apache. Not in the README, not in the filename or the directory it expands into, not in the html docs. (Only a breadcrumb at the top and the copyright notice at the bottom.) So... adjust the TMs as needed, if you want. Thanks! (There are two small unrelated changes in that patch -- one spelling fix, and I changed the version number on the 'tab' from 3.4 to 3.5.) > Update docs for Apache branding and trademark requirements > -- > > Key: ZOOKEEPER-2071 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2071 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Wendy Smoak >Assignee: Wendy Smoak > Attachments: ZOOKEEPER-2071-1.diff > > > The documentation needs to follow the Apache branding and trademark > requirements: http://www.apache.org/foundation/marks/pmcs.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201343#comment-14201343 ] Jian Fang commented on ZOOKEEPER-1044: -- BTW, I wonder if it is possible for zookeeper to manage the role change by itself in the future. For example, I can specify that I only expect 5 participants in normal operations. The zookeeper peers can make an election on which peers should be participants and which should be observers by themselves. Also do the election once participants are lost. In this way, I can simply start up 8 zookeeper instances, for instance. And I don't need any management tool or code to babysit the zookeeper quorum. I think this should dramatically reduce the operational overhead especially when people run zookeeper in cloud because a cloud instance could be gone forever and at any time. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201169#comment-14201169 ] Jian Fang commented on ZOOKEEPER-1044: -- Alexander, thanks for your clarification. I think I should use more participants in odd number to tolerant multiple node failures before only two participants are left. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201155#comment-14201155 ] Alexander Shraer commented on ZOOKEEPER-1044: - I mean leader proposals > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201154#comment-14201154 ] Alexander Shraer commented on ZOOKEEPER-1044: - Yeah I was talking just about participants. Only participants are involved in voting. So what I mean is that having 6 participants doesn't add to the fault tolerance compared to 5 participants. In case you have X servers you need to decide how many concurrent failures you want to tolerate (t), make 2t+1 servers participants and the rest X - (2t + 1) observers. BTW when a server fails its still in the ensemble logically. The "voting" in zookeeper are just ACKs of server proposals. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201106#comment-14201106 ] Jian Fang commented on ZOOKEEPER-1044: -- Thanks Hongchao and Alexander for your quick response. Alexander, I am still a bit confused while you said 5 servers can tolerate a failure of 2 and 6 servers can tolerate only 2 failures. Do the 5 servers and 6 servers include observers as well? From documents, seems only participants are involved in the voting, right? Do you mean 5 participants and 6 participants? If that is true, do you suggest I set all 6 peers to be participants instead of 3 participants and 3 observers? Also, let us consider we have 4 participants, do we have a scenario that 2 peers have the same vote, but different from the other two? Or this is not possible because zookeeper always uses a leader? Thanks again. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201080#comment-14201080 ] Alexander Shraer commented on ZOOKEEPER-1044: - also see ZOOKEEPER-1660 for documentation. > If I understand correctly, zookeeper must keep the number of participants to > be an odd number to avoid a tie > condition. no, it doesn't matter for zookeeper whether its odd or even. Its recommended to keep it odd since zookeeper needs a majority of servers up and running to work, so for example if you have 5 servers you can tolerate a failure of 2. But if you have 6 servers you can also tolerate only 2 failures, so in terms of fault tolerance having 6 vs having 5 doesn't give you anything. If one participant out of 3 is down you can't tolerate any more failures - any other failure will bring your ensemble down. You can do a reconfig in which you remove the faulty server and change an observer into a participant. In the docs notice the corner case explained in Sec 4.2.6 (Changing an observer into a follower) - in some cases you may need to first remove the observer (logically, using a reconfig) and then add it back as a participant. Usually you can do just one command though. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201048#comment-14201048 ] Hongchao Deng commented on ZOOKEEPER-1044: -- https://github.com/apache/zookeeper/blob/trunk/src/java/test/org/apache/zookeeper/test/ReconfigTest.java#L485 You just need to append the role (e.g. "observer" or "participant") to the string and ZK will parse it. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201043#comment-14201043 ] Jian Fang commented on ZOOKEEPER-1044: -- I am using 3.5.0-alpha from the central Maven repository, but it is not clear to me which API I should call to make this change. I saw some test cases in Zookeeper to create a ZK client and then call the following method in Zookeeper, public byte[] reconfig(List joiningServers, List leavingServers, List newMembers, long fromConfig, Stat stat) throws KeeperException, InterruptedException How do I specify the roles for the peers then? Thanks. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200932#comment-14200932 ] Hongchao Deng commented on ZOOKEEPER-1044: -- [~john.jian.fang] You can do this in 3.5.X versions or later. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1044) Allow dynamic changes to roles of a peer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200862#comment-14200862 ] Jian Fang commented on ZOOKEEPER-1044: -- Hi, I have a use case to dynamically change a role of a peer from observer to participant. Here is my scenario. I run the zookeeper quorum in cloud and some nodes may be terminated by the cloud. The lost node could be replaced with a new node after some time. If I understand correctly, zookeeper must keep the number of participants to be an odd number to avoid a tie condition. For example, assume that I have 3 participants and 3 observers. If I lost one participant, usually how long could zookeeper survive with only two 2 participants? To solve the problem with two participants, I am thinking of changing one observer to be a participant to keep the number of participants to be 3. Would this be a valid use case for zookeeper? Since this ticket has already been closed, I like to confirm if this is doable in 3.5.0 and what is the API to change the roles programmatically if it is doable. Thanks in advance. > Allow dynamic changes to roles of a peer > > > Key: ZOOKEEPER-1044 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044 > Project: ZooKeeper > Issue Type: Sub-task > Components: quorum >Affects Versions: 3.3.0 >Reporter: Vishal Kher >Assignee: Alexander Shraer > Fix For: 3.5.0 > > > Requirement: functionality that will reconfigure > a OBSERVER to become a voting member and vice versa. > Example of usage: > 1. Maintain the Quorum size without changing the cluster size - in a 5 > node cluster with 2 observers, I decide to decommission a voting > member. Then, I would like to configure one of my observers to be a > follower without any down time. > 2. Added a new server to the cluster that has better resources than > one of the voting peers. Make the new node as voting peer and the old > one as observer. > 3. Reduce the size of voting member for performance reasons. > Fix to ZOOKEEPER-107 might automatically give us this functionality. > It will be good to confirm that, and if needed, highlight work > that might be needed in addition to ZOOKEEPER-107. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-openjdk7 - Build # 622 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/622/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 328020 lines...] [junit] 2014-11-06 20:27:03,231 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2014-11-06 20:27:03,232 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-11-06 20:27:03,233 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-11-06 20:27:03,233 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2014-11-06 20:27:03,233 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-11-06 20:27:03,234 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-11-06 20:27:03,234 [myid:] - INFO [main:ZooKeeperServer@781] - minSessionTimeout set to 6000 [junit] 2014-11-06 20:27:03,234 [myid:] - INFO [main:ZooKeeperServer@790] - maxSessionTimeout set to 6 [junit] 2014-11-06 20:27:03,234 [myid:] - INFO [main:ZooKeeperServer@152] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test3936226691723672792.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test3936226691723672792.junit.dir/version-2 [junit] 2014-11-06 20:27:03,235 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test3936226691723672792.junit.dir/version-2/snapshot.b [junit] 2014-11-06 20:27:03,238 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test3936226691723672792.junit.dir/version-2/snapshot.b [junit] 2014-11-06 20:27:03,240 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-11-06 20:27:03,241 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:33771 [junit] 2014-11-06 20:27:03,242 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:33771 [junit] 2014-11-06 20:27:03,242 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-11-06 20:27:03,243 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:33771 (no session established for client) [junit] 2014-11-06 20:27:03,243 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-11-06 20:27:03,245 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-11-06 20:27:03,245 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2014-11-06 20:27:03,245 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-11-06 20:27:03,245 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2014-11-06 20:27:03,246 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 85675 [junit] 2014-11-06 20:27:03,246 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2014-11-06 20:27:03,246 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-11-06 20:27:03,246 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-11-06 20:27:03,308 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x14986c9f5f1 closed [junit] 2014-11-06 20:27:03,308 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-11-06 20:27:03,308 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-11-06 20:27:03,309 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2014-11-06 20:27:03,309 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-11-06 20:27:03,309 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2014-11-06 20:27:03,309 [myid:] - INFO [NIOServerCxnFactory
[jira] [Commented] (ZOOKEEPER-2071) Update docs for Apache branding and trademark requirements
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200559#comment-14200559 ] Flavio Junqueira commented on ZOOKEEPER-2071: - The patch looks good to me, I'll update the docs with the sentence you're asking for and will upload a new patch, [~wsmoak]. > Update docs for Apache branding and trademark requirements > -- > > Key: ZOOKEEPER-2071 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2071 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Wendy Smoak >Assignee: Wendy Smoak > Attachments: ZOOKEEPER-2071-1.diff > > > The documentation needs to follow the Apache branding and trademark > requirements: http://www.apache.org/foundation/marks/pmcs.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2071) Update docs for Apache branding and trademark requirements
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated ZOOKEEPER-2071: Assignee: Wendy Smoak > Update docs for Apache branding and trademark requirements > -- > > Key: ZOOKEEPER-2071 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2071 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Wendy Smoak >Assignee: Wendy Smoak > Attachments: ZOOKEEPER-2071-1.diff > > > The documentation needs to follow the Apache branding and trademark > requirements: http://www.apache.org/foundation/marks/pmcs.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2064) Prevent resource leak in various classes
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] melissa h updated ZOOKEEPER-2064: - Priority: Critical (was: Major) > Prevent resource leak in various classes > > > Key: ZOOKEEPER-2064 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2064 > Project: ZooKeeper > Issue Type: Bug >Reporter: Ted Yu >Priority: Critical > Attachments: 2064-v1.txt > > > In various classes, there is potential resource leak. > e.g. LogIterator / RandomAccessFileReader is not closed upon return from the > method. > Corresponding close() should be called to prevent resource leak. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2071) Update docs for Apache branding and trademark requirements
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] melissa h updated ZOOKEEPER-2071: - Issue Type: Bug (was: Task) Hadoop Flags: Incompatible change > Update docs for Apache branding and trademark requirements > -- > > Key: ZOOKEEPER-2071 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2071 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Wendy Smoak > Attachments: ZOOKEEPER-2071-1.diff > > > The documentation needs to follow the Apache branding and trademark > requirements: http://www.apache.org/foundation/marks/pmcs.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-jdk8 - Build # 193 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/193/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 336812 lines...] [junit] 2014-11-06 12:18:58,551 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-11-06 12:18:58,551 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-11-06 12:18:58,551 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2014-11-06 12:18:58,552 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-11-06 12:18:58,552 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-11-06 12:18:58,552 [myid:] - INFO [main:ZooKeeperServer@781] - minSessionTimeout set to 6000 [junit] 2014-11-06 12:18:58,553 [myid:] - INFO [main:ZooKeeperServer@790] - maxSessionTimeout set to 6 [junit] 2014-11-06 12:18:58,553 [myid:] - INFO [main:ZooKeeperServer@152] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8147349962982359589.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8147349962982359589.junit.dir/version-2 [junit] 2014-11-06 12:18:58,554 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8147349962982359589.junit.dir/version-2/snapshot.b [junit] 2014-11-06 12:18:58,556 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8147349962982359589.junit.dir/version-2/snapshot.b [junit] 2014-11-06 12:18:58,558 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-11-06 12:18:58,558 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:37667 [junit] 2014-11-06 12:18:58,559 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:37667 [junit] 2014-11-06 12:18:58,559 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-11-06 12:18:58,560 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:37667 (no session established for client) [junit] 2014-11-06 12:18:58,560 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-11-06 12:18:58,562 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-11-06 12:18:58,562 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2014-11-06 12:18:58,562 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-11-06 12:18:58,562 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2014-11-06 12:18:58,563 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 62024 [junit] 2014-11-06 12:18:58,563 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2014-11-06 12:18:58,563 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-11-06 12:18:58,563 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-11-06 12:18:58,624 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x149850b1c86 closed [junit] 2014-11-06 12:18:58,624 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-11-06 12:18:58,624 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-11-06 12:18:58,625 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-11-06 12:18:58,625 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2014-11-06 12:18:58,626 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-11-06 12:18:58,626 [myid:] - INFO [main:ZooKeeperServer@443] - shutting down [junit] 2014-11-06 12:18:58,627 [myid:] - INFO [main:SessionTrackerImpl
ZooKeeper-trunk - Build # 2493 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk/2493/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 330255 lines...] [junit] 2014-11-06 11:10:50,910 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:37663 [junit] 2014-11-06 11:10:50,910 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-11-06 11:10:50,911 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:37663 (no session established for client) [junit] 2014-11-06 11:10:50,911 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-11-06 11:10:50,913 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-11-06 11:10:50,913 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2014-11-06 11:10:50,913 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-11-06 11:10:50,914 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2014-11-06 11:10:50,914 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 83951 [junit] 2014-11-06 11:10:50,914 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2014-11-06 11:10:50,914 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-11-06 11:10:50,915 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-11-06 11:10:50,958 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x14984ccbcef closed [junit] 2014-11-06 11:10:50,958 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-11-06 11:10:50,958 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-11-06 11:10:50,959 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2014-11-06 11:10:50,958 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2014-11-06 11:10:50,959 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-11-06 11:10:50,959 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-11-06 11:10:50,960 [myid:] - INFO [main:ZooKeeperServer@443] - shutting down [junit] 2014-11-06 11:10:50,960 [myid:] - INFO [main:SessionTrackerImpl@231] - Shutting down [junit] 2014-11-06 11:10:50,960 [myid:] - INFO [main:PrepRequestProcessor@971] - Shutting down [junit] 2014-11-06 11:10:50,960 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2014-11-06 11:10:50,960 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop! [junit] 2014-11-06 11:10:50,961 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2014-11-06 11:10:50,961 [myid:] - INFO [main:FinalRequestProcessor@476] - shutdown of request processor complete [junit] 2014-11-06 11:10:50,962 [myid:] - INFO [main:MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree] [junit] 2014-11-06 11:10:50,962 [myid:] - INFO [main:MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11221] [junit] 2014-11-06 11:10:50,963 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-11-06 11:10:50,964 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2014-11-06 11:10:50,969 [myid:] - INFO [main:ClientBase@545] - fdcount after test is: 46 at start it was 33 [junit] 2014-11-06 11:10:50,969 [myid:] - INFO [main:ClientBase@547] - sleeping for 20 secs [junit] 2014-11-06 11:10:50,970 [myid:] - INFO [main:ZKTestCase$1@65] - SUCCEEDED testQuota [junit] 2014-11-06 11:10:50,970 [myid:] - INFO [main:ZKTestCase$1@60] - FINISHED testQuota [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.705 sec [junit] 2014-11-06 11:10:51,000 [myid:] - INFO [SessionTracker:SessionTrackerImpl@157] - SessionTrackerImpl exited loop! [junit] 2014-11-06 11:10:51,000 [myid:] - INFO [SessionTracker:SessionTrackerImpl@157] - SessionTrackerImpl exited loop! [junit] 2014-11-06 11:10:51,001
ZooKeeper-trunk-ibm6 - Build # 668 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-ibm6/668/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 354316 lines...] [junit] 2014-11-06 09:32:46,266 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2014-11-06 09:32:46,267 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-11-06 09:32:46,268 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-11-06 09:32:46,268 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2014-11-06 09:32:46,269 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-11-06 09:32:46,270 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-11-06 09:32:46,270 [myid:] - INFO [main:ZooKeeperServer@781] - minSessionTimeout set to 6000 [junit] 2014-11-06 09:32:46,271 [myid:] - INFO [main:ZooKeeperServer@790] - maxSessionTimeout set to 6 [junit] 2014-11-06 09:32:46,271 [myid:] - INFO [main:ZooKeeperServer@152] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test6725673524173493239.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test6725673524173493239.junit.dir/version-2 [junit] 2014-11-06 09:32:46,272 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test6725673524173493239.junit.dir/version-2/snapshot.b [junit] 2014-11-06 09:32:46,275 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test6725673524173493239.junit.dir/version-2/snapshot.b [junit] 2014-11-06 09:32:46,277 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-11-06 09:32:46,278 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:38046 [junit] 2014-11-06 09:32:46,279 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:38046 [junit] 2014-11-06 09:32:46,279 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-11-06 09:32:46,280 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:38046 (no session established for client) [junit] 2014-11-06 09:32:46,281 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-11-06 09:32:46,284 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-11-06 09:32:46,284 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2014-11-06 09:32:46,285 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-11-06 09:32:46,285 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2014-11-06 09:32:46,285 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 5243 [junit] 2014-11-06 09:32:46,286 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 40 [junit] 2014-11-06 09:32:46,286 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-11-06 09:32:46,286 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-11-06 09:32:46,313 [myid:] - INFO [main:ZooKeeper@968] - Session: 0x1498472f22f closed [junit] 2014-11-06 09:32:46,313 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down [junit] 2014-11-06 09:32:46,313 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-11-06 09:32:46,314 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2014-11-06 09:32:46,314 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2014-11-06 09:32:46,314 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2014-11-06 09:32:46,314 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIO
