[jira] Updated: (ZOOKEEPER-285) the stat command does not return the correct mode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-285: Affects Version/s: 3.0.0 3.0.1 Fix Version/s: 3.1.0 Assignee: Benjamin Reed the stat command does not return the correct mode - Key: ZOOKEEPER-285 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-285 Project: Zookeeper Issue Type: Bug Affects Versions: 3.0.0, 3.0.1 Reporter: Benjamin Reed Assignee: Benjamin Reed Fix For: 3.1.0 the stat command is always returning standalone it should return the actual mode it is in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-286) Make GenerateLoad use InstanceContainers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-286: Status: Open (was: Patch Available) cancelling patch to use svn mv for history on the files... Make GenerateLoad use InstanceContainers Key: ZOOKEEPER-286 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-286 Project: Zookeeper Issue Type: Improvement Affects Versions: 3.0.1, 3.0.0 Reporter: Benjamin Reed Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-286.patch GenerateLoad is a pain to setup and run. It would be nice if it used the same infrastructure as the system test so that we can more easily run performance tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-286) Make GenerateLoad use InstanceContainers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-286: Attachment: ZOOKEEPER-286.patch You have to svn move src/java/test/org/apache/zookeeper/test/GenerateLoad.java to src/java/systest/org/apache/zookeeper/test/system/GenerateLoad.java before applying this patch. Make GenerateLoad use InstanceContainers Key: ZOOKEEPER-286 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-286 Project: Zookeeper Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Benjamin Reed Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-286.patch, ZOOKEEPER-286.patch GenerateLoad is a pain to setup and run. It would be nice if it used the same infrastructure as the system test so that we can more easily run performance tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Hudson build is back to normal: ZooKeeper-trunk #217
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/217/changes
[jira] Commented: (ZOOKEEPER-231) Quotas in zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669745#action_12669745 ] Flavio Paiva Junqueira commented on ZOOKEEPER-231: -- +1. It looks good to me, it compiles without problems, and tests run fine. Quotas in zookeeper --- Key: ZOOKEEPER-231 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-231 Project: Zookeeper Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 3.1.0 Attachments: ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch, ZOOKEEPER-231.patch creating quota's in zookeeper so that a runaway application does not bring down the zookeeper cluster. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-286) Make GenerateLoad use InstanceContainers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-286: Attachment: ZOOKEEPER-286.patch the prev patch did not apply cleanly. you need to run svn mv as ben last stated adn then apply the patch. Make GenerateLoad use InstanceContainers Key: ZOOKEEPER-286 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-286 Project: Zookeeper Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Benjamin Reed Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-286.patch, ZOOKEEPER-286.patch, ZOOKEEPER-286.patch, ZOOKEEPER-286.patch GenerateLoad is a pain to setup and run. It would be nice if it used the same infrastructure as the system test so that we can more easily run performance tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-220) programming guide watches section should clarify server/clientlib role in data/child watch maint.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-220: Attachment: ZOOKEEPER-220.patch This patch makes some minor clarifications to that section. conceptually it is very helpful to think of two lists of watchers, so i don't think it would be wise to remove it. (internally it is actually a bit more complicated.) i added a bit more wording to appeal to the intuition. programming guide watches section should clarify server/clientlib role in data/child watch maint. - Key: ZOOKEEPER-220 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-220 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.0 Environment: http://hadoop.apache.org/zookeeper/docs/r3.0.0/zookeeperProgrammers.html#ch_zkWatchesonly Reporter: Patrick Hunt Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-220.patch http://hadoop.apache.org/zookeeper/docs/r3.0.0/zookeeperProgrammers.html#ch_zkWatches The server is maintaining two lists, it's not really clear in some sections that it's the server, esp as in v3 the client is also maintaining it's own list(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-220) programming guide watches section should clarify server/clientlib role in data/child watch maint.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-220: Affects Version/s: (was: 3.0.0) 3.1.0 Status: Patch Available (was: Open) programming guide watches section should clarify server/clientlib role in data/child watch maint. - Key: ZOOKEEPER-220 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-220 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.1.0 Environment: http://hadoop.apache.org/zookeeper/docs/r3.0.0/zookeeperProgrammers.html#ch_zkWatchesonly Reporter: Patrick Hunt Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-220.patch http://hadoop.apache.org/zookeeper/docs/r3.0.0/zookeeperProgrammers.html#ch_zkWatches The server is maintaining two lists, it's not really clear in some sections that it's the server, esp as in v3 the client is also maintaining it's own list(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-285) the stat command does not return the correct mode
the stat command does not return the correct mode - Key: ZOOKEEPER-285 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-285 Project: Zookeeper Issue Type: Bug Reporter: Benjamin Reed the stat command is always returning standalone it should return the actual mode it is in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-215) expand system test environment
[ https://issues.apache.org/jira/browse/ZOOKEEPER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669573#action_12669573 ] Hudson commented on ZOOKEEPER-215: -- Integrated in ZooKeeper-trunk #217 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/217/]) expand system test environment -- Key: ZOOKEEPER-215 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-215 Project: Zookeeper Issue Type: New Feature Components: tests Reporter: Patrick Hunt Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-215.patch, ZOOKEEPER-215.patch, ZOOKEEPER-215.patch, ZOOKEEPER-215.patch, ZOOKEEPER-215.patch, ZOOKEEPER-215.patch Currently our system tests are lumped in with our unit tests. It would be great to have a system test environment where we could run larger scale testing. Say you have 20 hosts, and you would like to test a serving ensemble with 7 servers and 100 clients running particular operations. It should be easy to test this scenario. Additionally during the test it should be possible to simulate serving node failure, etc... I've had a brief conversation with Ben about this and he's going to take this JIRA. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-286) Make GenerateLoad use InstanceContainers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-286: Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) I just committed this. Thanks Ben. Make GenerateLoad use InstanceContainers Key: ZOOKEEPER-286 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-286 Project: Zookeeper Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Benjamin Reed Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-286.patch, ZOOKEEPER-286.patch, ZOOKEEPER-286.patch, ZOOKEEPER-286.patch GenerateLoad is a pain to setup and run. It would be nice if it used the same infrastructure as the system test so that we can more easily run performance tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-284) JMX doesn't get the clientPort correctly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar resolved ZOOKEEPER-284. - Resolution: Fixed Hadoop Flags: [Reviewed] ZOOKEEPER-286 has been committed. So closing this one. JMX doesn't get the clientPort correctly Key: ZOOKEEPER-284 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-284 Project: Zookeeper Issue Type: Bug Affects Versions: 3.1.0 Reporter: Benjamin Reed Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 The client port in JMX is always zero. it should be getting the client port from the cnxnfactory. it's a pretty easy fix. the really problem is that we have a setter for the clientPort as well, which is a bit more complicated to implement correctly. do we need a setter for the clientPort? i think we should make it a readonly attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-220) programming guide watches section should clarify server/clientlib role in data/child watch maint.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-220: --- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) Committed revision 740141. programming guide watches section should clarify server/clientlib role in data/child watch maint. - Key: ZOOKEEPER-220 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-220 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.1.0 Environment: http://hadoop.apache.org/zookeeper/docs/r3.0.0/zookeeperProgrammers.html#ch_zkWatchesonly Reporter: Patrick Hunt Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-220.patch, ZOOKEEPER-220.patch http://hadoop.apache.org/zookeeper/docs/r3.0.0/zookeeperProgrammers.html#ch_zkWatches The server is maintaining two lists, it's not really clear in some sections that it's the server, esp as in v3 the client is also maintaining it's own list(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-272) getChildren can fail for large numbers of children
[ https://issues.apache.org/jira/browse/ZOOKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669570#action_12669570 ] Hudson commented on ZOOKEEPER-272: -- Integrated in ZooKeeper-trunk #217 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/217/]) getChildren can fail for large numbers of children -- Key: ZOOKEEPER-272 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-272 Project: Zookeeper Issue Type: Bug Reporter: Joshua Tuberville Assignee: Mahadev konar Fix For: 3.1.0 Attachments: ZOOKEEPER-272.patch Zookeeper allows creation of an abritrary number of children, yet if the String array of children names exceeds 4,194,304 bytes a getChildren will fail because ClientCnxn$SendThread.readLength() throws an exception on line 490. Mahadev Konar questioned this byte limit's need. In any case consistency of create children, get children should exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-260) document the recommended values for server id's
[ https://issues.apache.org/jira/browse/ZOOKEEPER-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669572#action_12669572 ] Hudson commented on ZOOKEEPER-260: -- Integrated in ZooKeeper-trunk #217 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/217/]) document the recommended values for server id's --- Key: ZOOKEEPER-260 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-260 Project: Zookeeper Issue Type: Improvement Affects Versions: 3.0.0, 3.0.1 Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 3.1.0 Attachments: ZOOKEEPER-260.patch, ZOOKEEPER-260.patch currently we do nto doucment the recommended values for server id's. we should document that. For some large values of server id's we might get negative session's and also might get duplicate sessions from two servers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-275) Bug in FastLeaderElection
[ https://issues.apache.org/jira/browse/ZOOKEEPER-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669568#action_12669568 ] Hudson commented on ZOOKEEPER-275: -- Integrated in ZooKeeper-trunk #217 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/217/]) Bug in FastLeaderElection - Key: ZOOKEEPER-275 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-275 Project: Zookeeper Issue Type: Bug Components: leaderElection Affects Versions: 3.0.0, 3.0.1 Reporter: Flavio Paiva Junqueira Assignee: Flavio Paiva Junqueira Fix For: 3.1.0 Attachments: ZOOKEEPER-275.patch, ZOOKEEPER-275.patch, ZOOKEEPER-275.patch, ZOOKEEPER-275.patch I found an execution in which leader election does not make progress. Here is the problematic scenario: - We have an ensemble of 3 servers, and we start only 2; - We let them elect a leader, and then crash the one with lowest id, say S_1 (call the other S_2); - We restart the crashed server. Upon restarting S_1, S_2 has its logical clock more advanced, and S_1 has its logical clock set to 1. Once S_1 receives a notification from S_2, it notices that it is in the wrong round and it advances its logical clock to the same value as S_1. Now, the problem comes exactly in this point because in the current code S_1 resets its vote to its initial vote (its own id and zxid). Since S_2 has already notified S_1, it won't do it again, and we are stuck. The patch I'm submitting fixes this problem by setting the vote of S_1 to the one received if it satisfies the total order predicate (received zxid is higher or received zxid is the same and received id is higher). Related to this problem, I noticed that by trying to avoid unnecessary notification duplicates, there could be scenarios in which a server fails before electing a leader and restarts before leader election succeeds. This could happen, for example, when there isn't enough servers available and one available crashes and restarts. I fixed this problem in the attached patch by allowing a server to send a new batch of notifications if there is at least one outgoing queue of pending notifications empty. This is ok because we space out consecutive batches of notifications. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-229) improve documentation regarding user's responsibility to cleanup datadir (snaps/logs)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669569#action_12669569 ] Hudson commented on ZOOKEEPER-229: -- Integrated in ZooKeeper-trunk #217 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/217/]) improve documentation regarding user's responsibility to cleanup datadir (snaps/logs) - Key: ZOOKEEPER-229 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-229 Project: Zookeeper Issue Type: Improvement Components: documentation, server Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Mahadev konar Fix For: 3.1.0 Attachments: ZOOKEEPER-229.patch, ZOOKEEPER-229.patch It's not very obvious in the docs that the operator of the zk server is responsible for managing the files in the datadir: http://hadoop.apache.org/zookeeper/docs/r3.0.0/zookeeperAdmin.html#File+Management specifically removing the old snaps/transactionallogs we need to make this more obvious, perhaps call it out in the quickstart (note pointing to this document) Perhaps we should include example script and cron as well (docs) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-276) Bookkeeper contribution
[ https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669575#action_12669575 ] Hudson commented on ZOOKEEPER-276: -- Integrated in ZooKeeper-trunk #217 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/217/]) Bookkeeper contribution --- Key: ZOOKEEPER-276 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-276 Project: Zookeeper Issue Type: New Feature Reporter: Luca Telloli Assignee: Flavio Paiva Junqueira Fix For: 3.1.0 Attachments: ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch BookKeeper is a system to reliably log streams of records. In BookKeeper, servers are bookies, log streams are ledgers, and each unit of a log (aka record) is a ledger entry. BookKeeper is designed to be reliable; bookies, the servers that store ledgers can be byzantine, which means that some subset of the bookies can fail, corrupt data, discard data, but as long as there are enough correctly behaving servers the service as a whole behaves correctly; the meta data for BookKeeper is stored in ZooKeeper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-69: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed revision 740112. Committed revision 740193. ZooKeeper logo -- Key: ZOOKEEPER-69 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 Project: Zookeeper Issue Type: Wish Components: documentation Reporter: Flavio Paiva Junqueira Assignee: Benjamin Reed Priority: Minor Fix For: 3.1.0 Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png, zookeeper-sketch.jpg I think we need a cool logo for the project. The ones I've seen so far are a little lame, and that includes the one I've created for SourceForge. If anyone on this list has an idea or knows of anyone with some art skills, plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-287) high cpu utilization caused by nioserver factory thread
high cpu utilization caused by nioserver factory thread --- Key: ZOOKEEPER-287 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-287 Project: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.0.1 Environment: Linux 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:58:04 EST 2007 i686 i686 i386 GNU/Linux the servers were running in vmware vms java version 1.6.0_06 Java(TM) SE Runtime Environment (build 1.6.0_06-b02) Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode) Reporter: Patrick Hunt Priority: Critical a user reported that a long running server, part of a 2 server ensemble, started using 100%cpu (1 server of the ensemble, the other was fine). mahadev tracked it down to a thread in the server running epoll in a tight loop - the thread was the nio server factory thread that selects on client fds. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
