[jira] Commented: (ZOOKEEPER-253) documentation of DataWatcher state transition is misleading regarding auto watch reset on reconnect
[ https://issues.apache.org/jira/browse/ZOOKEEPER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668003#action_12668003 ] Hudson commented on ZOOKEEPER-253: -- Integrated in ZooKeeper-trunk #212 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/212/]) . documentation of DataWatcher state transition is misleading regarding auto watch reset on reconnect. (phunt via mahadev) documentation of DataWatcher state transition is misleading regarding auto watch reset on reconnect --- Key: ZOOKEEPER-253 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-253 Project: Zookeeper Issue Type: Bug Components: documentation Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-253.patch the example code has case SyncConnected: // Everything is happy. Lets kick things off // again by checking the existence of the znode break; this is misleading - it should indicate that the watches are automatically reset and therefor no call to exists is necessary also fix this in the same doc (looks like its old detail, no longer valid), indicate that autoreset will happen on reconnect. If the client-side ZooKeeper libraries can reestablish the communication channel to ZooKeeper, DataMonitor simply kicks everything off again with the call to ZooKeeper.exists(). If it gets an event for a znode, it calls ZooKeeper.exists() to find out what has changed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-177) needed: docs for JMX
[ https://issues.apache.org/jira/browse/ZOOKEEPER-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668004#action_12668004 ] Hudson commented on ZOOKEEPER-177: -- Integrated in ZooKeeper-trunk #212 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/212/]) . needed: docs for JMX (phunt via mahadev) needed: docs for JMX Key: ZOOKEEPER-177 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-177 Project: Zookeeper Issue Type: Improvement Components: documentation, jmx Reporter: Robbie Scott Assignee: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-177.patch I don't know if this should be part of the logging section in the zookeeper admin guide (see JIRA ZOOKEEPER-166 ) but, per Patrick, related to security, ack, yea another doc, is the documentation of the JMX support that zk has -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-276) Bookkeeper contribution
[ https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Telloli updated ZOOKEEPER-276: --- Attachment: (was: ZOOKEEPER-276.patch) 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 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-269) connectionloss - add more documentation to detail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-269: - Attachment: ZOOKEEPER-269.patch I just made a few editorial changes. connectionloss - add more documentation to detail -- Key: ZOOKEEPER-269 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-269 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Assignee: Flavio Paiva Junqueira Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-269.patch, ZOOKEEPER-269.patch discussion with user, this should be better documented: -- There are basically 2 cases where you can see connectionloss: 1) you call an operation on a session that is no longer alive 2) you are disconnected from a server when there are pending async operations to that server (you made an async request which has not yet completed) Patrick Kevin Burton wrote: Can this be thrown when using multiple servers as long as 1 of them is online? Trying to figure out of I should try some type of reconnect if a single machine fails instead of failing altogether. Kevin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-269) connectionloss - add more documentation to detail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-269: - Attachment: ZOOKEEPER-269.patch connectionloss - add more documentation to detail -- Key: ZOOKEEPER-269 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-269 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Assignee: Flavio Paiva Junqueira Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-269.patch, ZOOKEEPER-269.patch, ZOOKEEPER-269.patch discussion with user, this should be better documented: -- There are basically 2 cases where you can see connectionloss: 1) you call an operation on a session that is no longer alive 2) you are disconnected from a server when there are pending async operations to that server (you made an async request which has not yet completed) Patrick Kevin Burton wrote: Can this be thrown when using multiple servers as long as 1 of them is online? Trying to figure out of I should try some type of reconnect if a single machine fails instead of failing altogether. Kevin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-269) connectionloss - add more documentation to detail
[ https://issues.apache.org/jira/browse/ZOOKEEPER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-269: - Status: Patch Available (was: Open) connectionloss - add more documentation to detail -- Key: ZOOKEEPER-269 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-269 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.1, 3.0.0 Reporter: Patrick Hunt Assignee: Flavio Paiva Junqueira Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-269.patch, ZOOKEEPER-269.patch, ZOOKEEPER-269.patch discussion with user, this should be better documented: -- There are basically 2 cases where you can see connectionloss: 1) you call an operation on a session that is no longer alive 2) you are disconnected from a server when there are pending async operations to that server (you made an async request which has not yet completed) Patrick Kevin Burton wrote: Can this be thrown when using multiple servers as long as 1 of them is online? Trying to figure out of I should try some type of reconnect if a single machine fails instead of failing altogether. Kevin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Deleted: (ZOOKEEPER-280) Re-distributable bundle zookeeper-3.0.1.tar.gz lacks some important files for c-lib build .
[ https://issues.apache.org/jira/browse/ZOOKEEPER-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim P. Dementiev deleted ZOOKEEPER-280: - Re-distributable bundle zookeeper-3.0.1.tar.gz lacks some important files for c-lib build . --- Key: ZOOKEEPER-280 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-280 Project: Zookeeper Issue Type: Bug Environment: Linux Reporter: Maxim P. Dementiev There is no configure (try: find zookeeper-3.0.1 -name configure) which is needed for build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-231) Quotas in zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-231: Attachment: ZOOKEEPER-231.patch Refactored the QuorumTest to create a quorumBase class like clientbase. Had to make some changes in the testcases to get it to working after the refactoring. 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 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-276) Bookkeeper contribution
[ https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-276: - Attachment: ZOOKEEPER-276.patch Implemented Mahadev suggestions. 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 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] Commented: (ZOOKEEPER-276) Bookkeeper contribution
[ https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668228#action_12668228 ] Flavio Paiva Junqueira commented on ZOOKEEPER-276: -- Forgot to mention that unit tests pass just fine for me. 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 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-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:all-tabpanel ] Mahadev konar updated ZOOKEEPER-229: Attachment: ZOOKEEPER-229.patch this patch adds appropriate docs to getting started and zookeeperadmin. 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 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] Updated: (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:all-tabpanel ] Mahadev konar updated ZOOKEEPER-229: Status: Patch Available (was: Open) 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 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] Updated: (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:all-tabpanel ] Mahadev konar updated ZOOKEEPER-272: Attachment: ZOOKEEPER-272.patch this patch allows tthe user to set java property jute.maxbuffer at the client. This value is used at the client to throw an error if the read len of value exceeds the set value. By default its set to 4MB. if the user wants to cahnge this value, he can do it via setting java property -Djute.maxbuffer=someintvalue 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] Updated: (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:all-tabpanel ] Mahadev konar updated ZOOKEEPER-272: Status: Patch Available (was: Open) 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] Updated: (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:all-tabpanel ] Mahadev konar updated ZOOKEEPER-260: Status: Patch Available (was: Open) 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.1, 3.0.0 Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 3.1.0 Attachments: 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] Updated: (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:all-tabpanel ] Mahadev konar updated ZOOKEEPER-260: Attachment: ZOOKEEPER-260.patch this patch adds docs for recommended values of server ids. 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 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.