[jira] Commented: (ZOOKEEPER-243) add SEQUENCE flag documentation to the programming guide
[ https://issues.apache.org/jira/browse/ZOOKEEPER-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655210#action_12655210 ] Hudson commented on ZOOKEEPER-243: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) . add SEQUENCE flag documentation to the programming guide. (patrick hunt via mahadev) add SEQUENCE flag documentation to the programming guide Key: ZOOKEEPER-243 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-243 Project: Zookeeper Issue Type: Improvement 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-243.patch There doesn't seem to be any docs in forrest detailing the sequence flag for node creation. In particular we should detail how the flag works, the naming format, and also rollover (when does the number roll over to 0 again). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-248) QuorumPeer should use Map interface instead of HashMap implementation.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655212#action_12655212 ] Hudson commented on ZOOKEEPER-248: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) QuorumPeer should use Map interface instead of HashMap implementation. -- Key: ZOOKEEPER-248 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-248 Project: Zookeeper Issue Type: Improvement Components: quorum Affects Versions: 3.0.0, 3.0.1 Reporter: Nitay Joffe Assignee: Nitay Joffe Priority: Trivial Fix For: 3.1.0 Attachments: 248.patch Using HashMap directly to store quorumPeers member variable unnecessarily decides for the user what implementation of Map to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-161) Content needed: Designing a ZooKeeper Deployment
[ https://issues.apache.org/jira/browse/ZOOKEEPER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655208#action_12655208 ] Hudson commented on ZOOKEEPER-161: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) . Content needed: Designing a ZooKeeper Deployment Content needed: Designing a ZooKeeper Deployment -- Key: ZOOKEEPER-161 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161 Project: Zookeeper Issue Type: Sub-task Components: documentation Affects Versions: 3.0.1 Reporter: Robbie Scott Assignee: Benjamin Reed Fix For: 3.1.0 Attachments: ZOOKEEPER-161.patch, ZOOKEEPER-161.patch Original Estimate: 8h Remaining Estimate: 8h We should document how ops engineer should design their ZooKeeper deployments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-245) update readme/quickstart to be release tar, rather than source, based
[ https://issues.apache.org/jira/browse/ZOOKEEPER-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655211#action_12655211 ] Hudson commented on ZOOKEEPER-245: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) . update readme/quickstart to be release tar, rather than source, based (patrick hunt via mahadev) update readme/quickstart to be release tar, rather than source, based - Key: ZOOKEEPER-245 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-245 Project: Zookeeper Issue Type: Bug Components: documentation Affects Versions: 3.0.1 Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-245.patch Owen O'Malley mentioned: - we need to change both the README and quick start to assume you are working with a release instead of a source tarball. Apache releases are the approved way of getting the project. Documentation that assumes they are getting source themselves doesn't reflect that. - -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-16) Need to do path validation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-16: -- Attachment: ZOOKEEPER-16.patch Updated patch based on comment/feedback. We now throw IllegalArgumentException in the java client if the path is not valid In the c client we return a rc of ZBADARGUMENT (c client was already checking for null - just added the addl conditions) Tests added to both c and java. Note: valid path definition already existed in the programmer guide, no additional doc changes were necessary -- although I did update the java and c client API docs as appropriate. Need to do path validation -- Key: ZOOKEEPER-16 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-16 Project: Zookeeper Issue Type: Bug Components: c client, java client, server Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-16.patch, ZOOKEEPER-16.patch Moved from SourceForge to Apache. http://sourceforge.net/tracker/index.php?func=detailaid=1963141group_id=209147atid=1008544 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters
[ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-225: --- Attachment: ZOOKEEPER-225.patch This patch adds info logs to both the c and java clients detailing the connection parameters - useful in certain debugging situations. c client should log an info message in zookeeper_init detailing connection parameters - Key: ZOOKEEPER-225 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225 Project: Zookeeper Issue Type: Improvement Components: c client Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-225.patch I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters
[ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-225: --- Assignee: Patrick Hunt Affects Version/s: 3.0.1 Status: Patch Available (was: Open) c client should log an info message in zookeeper_init detailing connection parameters - Key: ZOOKEEPER-225 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225 Project: Zookeeper Issue Type: Improvement Components: c client Affects Versions: 3.0.1, 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-225.patch I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-214) add new stat reset command to server admin port
[ https://issues.apache.org/jira/browse/ZOOKEEPER-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-214: --- Attachment: ZOOKEEPER-214.patch Added 'srst' or stat reset command to the list of 4 letter words supported by the command port. add new stat reset command to server admin port - Key: ZOOKEEPER-214 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-214 Project: Zookeeper Issue Type: Improvement Components: server Reporter: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-214.patch A new command should be added to the server admin port (client port) that allows users to reset the stats. We saw cases during troubleshooting where we would have liked to reset the min/avg/max latency stats, but were unable to do so (short of restarting the server). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-214) add new stat reset command to server admin port
[ https://issues.apache.org/jira/browse/ZOOKEEPER-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-214: -- Assignee: Patrick Hunt add new stat reset command to server admin port - Key: ZOOKEEPER-214 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-214 Project: Zookeeper Issue Type: Improvement Components: server Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-214.patch A new command should be added to the server admin port (client port) that allows users to reset the stats. We saw cases during troubleshooting where we would have liked to reset the min/avg/max latency stats, but were unable to do so (short of restarting the server). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-214) add new stat reset command to server admin port
[ https://issues.apache.org/jira/browse/ZOOKEEPER-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-214: --- Status: Patch Available (was: Open) add new stat reset command to server admin port - Key: ZOOKEEPER-214 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-214 Project: Zookeeper Issue Type: Improvement Components: server Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-214.patch A new command should be added to the server admin port (client port) that allows users to reset the stats. We saw cases during troubleshooting where we would have liked to reset the min/avg/max latency stats, but were unable to do so (short of restarting the server). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
