[jira] Commented: (ZOOKEEPER-8) Stat enchaned to include num of children and size
[ https://issues.apache.org/jira/browse/ZOOKEEPER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637382#action_12637382 ] Mahadev konar commented on ZOOKEEPER-8: --- +1 the patch looks good > Stat enchaned to include num of children and size > - > > Key: ZOOKEEPER-8 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-8 > Project: Zookeeper > Issue Type: Bug > Components: c client, java client >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Minor > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-8_1.patch, ZOOKEEPER-8_1.patch, > ZOOKEEPER-8_1.patch > > > Moved from SourceForge to Apache. > http://sourceforge.net/tracker/index.php?func=detail&aid=1886743&group_id=209147&atid=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-168) Programmer's Guide "Basic Operations" section is missing content
[ https://issues.apache.org/jira/browse/ZOOKEEPER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-168: --- Attachment: ZOOKEEPER-168.patch This patch has new place-holder sections for each of the missing content pieces that the jira talks about. Also, I attempted to merge in Patrick's recent docbook->sdoc changes. > Programmer's Guide "Basic Operations" section is missing content > > > Key: ZOOKEEPER-168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-168 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Reporter: Robbie Scott > Attachments: ZOOKEEPER-168.patch > > > There is a chapter in the ZooKeeper Programmer's Guide called: "Building > Blocks: A Guide to ZooKeeper Operations" that currently contains no content. > The idea behind this section is document all the basic things you can do with > the ZooKeeper API -- not every little detail, or even every call in the API, > but the basics, like: how to connect to a server, how to read a node, how to > write to a node, how to set a watch, etc. I will create a subtask for every > section in this chapter. > I don't mind writing up the these sections, if I can get the information, > whether its' by phone, email, im, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-168) Programmer's Guide "Basic Operations" section is missing content
[ https://issues.apache.org/jira/browse/ZOOKEEPER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-168: --- Attachment: (was: ZOOKEEPER-168.patch) > Programmer's Guide "Basic Operations" section is missing content > > > Key: ZOOKEEPER-168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-168 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Reporter: Robbie Scott > > There is a chapter in the ZooKeeper Programmer's Guide called: "Building > Blocks: A Guide to ZooKeeper Operations" that currently contains no content. > The idea behind this section is document all the basic things you can do with > the ZooKeeper API -- not every little detail, or even every call in the API, > but the basics, like: how to connect to a server, how to read a node, how to > write to a node, how to set a watch, etc. I will create a subtask for every > section in this chapter. > I don't mind writing up the these sections, if I can get the information, > whether its' by phone, email, im, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-160) Admin / Ops Guide Missing Content
[ https://issues.apache.org/jira/browse/ZOOKEEPER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-160: --- Attachment: ZOOKEEPER-160.patch this patch has blank place holder sections for each of the missing pieces of content that this jira discusses. I also tried to merge in Patrick's docbook->sdoc changes. > Admin / Ops Guide Missing Content > - > > Key: ZOOKEEPER-160 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-160 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Reporter: Robbie Scott > Attachments: ZOOKEEPER-160.patch > > > I'm adding new sections to the ZooKeeper Admin guide, but I don't have the > content to fill them out. These sections are: > - Designing a ZooKeeper Deployment > - Provisioning > - Things to Consider: ZooKeeper Strengths and Limitations > - Administering > - Monitoring > - Logging > - Troubleshooting > I'll add a subtask for each section. > Note: If the area experts prefer, I can conduct a phone interview or email > conversation or IM with them on the topic, and then write up the section so > they don't have to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-160) Admin / Ops Guide Missing Content
[ https://issues.apache.org/jira/browse/ZOOKEEPER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-160: --- Attachment: (was: ZOOKEEPER-160.patch) > Admin / Ops Guide Missing Content > - > > Key: ZOOKEEPER-160 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-160 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Reporter: Robbie Scott > > I'm adding new sections to the ZooKeeper Admin guide, but I don't have the > content to fill them out. These sections are: > - Designing a ZooKeeper Deployment > - Provisioning > - Things to Consider: ZooKeeper Strengths and Limitations > - Administering > - Monitoring > - Logging > - Troubleshooting > I'll add a subtask for each section. > Note: If the area experts prefer, I can conduct a phone interview or email > conversation or IM with them on the topic, and then write up the section so > they don't have to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-33) Better ACL management
[ https://issues.apache.org/jira/browse/ZOOKEEPER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-33: --- Attachment: ZOOKEEPER-33.patch here is a patch for this issue. its a preliminray patch. I will be adding tests. The patch does the following: has a mapping from long to acls in the datatree each datanode has a reference to acls. this only impacts the serialization and deserialization of acls on the datatree. > Better ACL management > - > > Key: ZOOKEEPER-33 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-33 > Project: Zookeeper > Issue Type: New Feature > Components: server >Reporter: Patrick Hunt >Assignee: Mahadev konar > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-33.patch > > > Moved from SourceForge to Apache. > http://sourceforge.net/tracker/index.php?func=detail&aid=1945175&group_id=209147&atid=1008547 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-168) Programmer's Guide "Basic Operations" section is missing content
[ https://issues.apache.org/jira/browse/ZOOKEEPER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-168: --- Attachment: ZOOKEEPER-168.patch This patch of the zookeeperProgrammers.xml has the new sections that need the content this JIRA talks about. As an aside, it's a little complicated by the fact that I'm trying to merge my changes with Patrick's changes to the sdoc docbook format. > Programmer's Guide "Basic Operations" section is missing content > > > Key: ZOOKEEPER-168 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-168 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Reporter: Robbie Scott > Attachments: ZOOKEEPER-168.patch > > > There is a chapter in the ZooKeeper Programmer's Guide called: "Building > Blocks: A Guide to ZooKeeper Operations" that currently contains no content. > The idea behind this section is document all the basic things you can do with > the ZooKeeper API -- not every little detail, or even every call in the API, > but the basics, like: how to connect to a server, how to read a node, how to > write to a node, how to set a watch, etc. I will create a subtask for every > section in this chapter. > I don't mind writing up the these sections, if I can get the information, > whether its' by phone, email, im, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-160) Admin / Ops Guide Missing Content
[ https://issues.apache.org/jira/browse/ZOOKEEPER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-160: --- Attachment: ZOOKEEPER-160.patch In this patch, I'm trying merge my changes in with Patricks simplified docbook, and also check in the new structure (that is, the empty sections) for the new topics that this JIRA talks about. > Admin / Ops Guide Missing Content > - > > Key: ZOOKEEPER-160 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-160 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Reporter: Robbie Scott > Attachments: ZOOKEEPER-160.patch > > > I'm adding new sections to the ZooKeeper Admin guide, but I don't have the > content to fill them out. These sections are: > - Designing a ZooKeeper Deployment > - Provisioning > - Things to Consider: ZooKeeper Strengths and Limitations > - Administering > - Monitoring > - Logging > - Troubleshooting > I'll add a subtask for each section. > Note: If the area experts prefer, I can conduct a phone interview or email > conversation or IM with them on the topic, and then write up the section so > they don't have to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-178) FLE test.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-178: Attachment: FLE-Fail.txt these are the logs that I saw FLE test failing with ant test. > FLE test. > - > > Key: ZOOKEEPER-178 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-178 > Project: Zookeeper > Issue Type: Bug > Components: leaderElection >Reporter: Mahadev konar > Fix For: 3.0.0 > > Attachments: FLE-Fail.txt > > > fast leader election test failing . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-178) FLE test.
FLE test. - Key: ZOOKEEPER-178 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-178 Project: Zookeeper Issue Type: Bug Reporter: Mahadev konar Fix For: 3.0.0 Attachments: FLE-Fail.txt fast leader election test failing . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-178) FLE test.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-178: Component/s: leaderElection > FLE test. > - > > Key: ZOOKEEPER-178 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-178 > Project: Zookeeper > Issue Type: Bug > Components: leaderElection >Reporter: Mahadev konar > Fix For: 3.0.0 > > Attachments: FLE-Fail.txt > > > fast leader election test failing . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-159) Cover two corner cases of leader election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-159: -- Assignee: Flavio Paiva Junqueira > Cover two corner cases of leader election > - > > Key: ZOOKEEPER-159 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-159 > Project: Zookeeper > Issue Type: Bug > Components: leaderElection >Reporter: Flavio Paiva Junqueira >Assignee: Flavio Paiva Junqueira > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-159.patch > > > In the default implementation of leader election, there are two undesirable > cases that need to be covered: > 1- If there is a leader elected and this leader is supported by at least > quorum of peers, then it can happen that one peer disconnects from the > leader, and initiates a new leader election. As it is a new leader election, > we increment the logical clock of this peer, and according to the current > implementation, this peer won't accept any vote from a peer with a lower LE > turn (corresponds to the value of the logical clock of the voting peer). The > attached patch corrects this problem by allowing a peer to go back to a > previous epoch in the case a majority votes for a leader, and the peer also > receives a vote from the leader. This feature allows a peer to correct a > false suspicion of the current leader; > 2- If a peer advances to a new turn before others, then it may end up voting > for a peer that either does not have the highest server id or the the highest > zxid. The attached patch fixes this problem by resetting the vote a peer when > it updates its logical clock upon receiving a notification with a higher turn > value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-176) needed: docs for auth plugin developers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-176: --- Component/s: documentation > needed: docs for auth plugin developers > > > Key: ZOOKEEPER-176 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-176 > Project: Zookeeper > Issue Type: Improvement > Components: documentation >Reporter: Robbie Scott > > Part of the interest in documentation related to security: > how to add different/new methods for integrating zk into existing auth > mechanisms, etc... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-177) needed: docs for JMX
needed: docs for JMX Key: ZOOKEEPER-177 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-177 Project: Zookeeper Issue Type: Improvement Components: documentation Reporter: Robbie Scott 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] Created: (ZOOKEEPER-176) needed: docs for auth plugin developers
needed: docs for auth plugin developers Key: ZOOKEEPER-176 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-176 Project: Zookeeper Issue Type: Improvement Reporter: Robbie Scott Part of the interest in documentation related to security: how to add different/new methods for integrating zk into existing auth mechanisms, etc... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-175) needed: docs for ops - how to setup acls & authentication in the server
needed: docs for ops - how to setup acls & authentication in the server --- Key: ZOOKEEPER-175 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-175 Project: Zookeeper Issue Type: Improvement Components: documentation Reporter: Robbie Scott Part of the interest in creating documentation related to security. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-174) Content needed: "Sync vs Async"
Content needed: "Sync vs Async" --- Key: ZOOKEEPER-174 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-174 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott Some time ago, Patrick suggested a subsection of the Basic Building Blocks section of the Programmer's Guide called "Sync vs. Async Operations." I don't know if that is still on the roadmap, but I put it here in case anyone wants to provide content for me to add to the Programmer's Guide. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-173) Content needed: "Miscellaneous Operations"
Content needed: "Miscellaneous Operations" -- Key: ZOOKEEPER-173 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-173 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott For lack of better term, I'm adding a section to the programmer's guide called "Miscellaneous Operations". This might eventually be broken out into sections of more descriptive terms. In short, these are COMMON zookeeper programming operations that do not come under the headings of connecting, reading, writing, or watching. (I don't think we should document uncommon or seldom used API here.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-172) Content needed: "Handling Watches"
Content needed: "Handling Watches" -- Key: ZOOKEEPER-172 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-172 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott We need the content which describes how client code should handle watches. Ideally this would have pseudo code describing any lead-up (for example resource allocation, etc), a few lines of sample code in Java, and a few parallel lines in C. Any commentary would be highly appreciated -- anything about handling watches that would not be obvious to a new ZooKeeper developer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-171) Content needed: "Write Operations"
Content needed: "Write Operations" -- Key: ZOOKEEPER-171 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-171 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott We need the content which describes how to a client should write data to a zookeeper node. Ideally this would have pseudo code describing any lead-up (for example resource allocation, etc), a few lines of sample code in Java, and a few parallel lines in C. Any commentary would be highly appreciated -- anything about writing data that would not be obvious to a new ZooKeeper developer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-170) Content needed: "Read Operations"
[ https://issues.apache.org/jira/browse/ZOOKEEPER-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-170: --- Remaining Estimate: 4h (was: 8h) Original Estimate: 4h (was: 8h) > Content needed: "Read Operations" > - > > Key: ZOOKEEPER-170 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-170 > Project: Zookeeper > Issue Type: Sub-task > Components: documentation >Reporter: Robbie Scott > Original Estimate: 4h > Remaining Estimate: 4h > > We need the content which describes how to a client should read data from a > zookeeper node. Ideally this would have pseudo code describing any lead-up > (for example resource allocation, etc), a few lines of sample code in Java, > and a few parallel lines in C. > Any commentary would be highly appreciated -- anything about reading data > that would not be obvious to a new ZooKeeper developer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-169) Content needed: "Connecting to ZooKeeper"
[ https://issues.apache.org/jira/browse/ZOOKEEPER-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-169: --- Remaining Estimate: 4h Original Estimate: 4h > Content needed: "Connecting to ZooKeeper" > - > > Key: ZOOKEEPER-169 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-169 > Project: Zookeeper > Issue Type: Sub-task > Components: documentation >Reporter: Robbie Scott > Original Estimate: 4h > Remaining Estimate: 4h > > We need the content which describes how to a client should connect to a > zookeeper server. Ideally this would have pseudo code describing any lead-up > (for example resource allocation, etc), a few lines of sample code in Java, > and a few parallel lines in C. > Any commentary would be highly appreciated. Stuff like, "You can open an > unlimited number of ZooKeeper connections because..." or "Opening too many > connections to ZooKeeper is not advisable because..." -- in short, anything > that is not obvious to the new ZooKeeper developer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-170) Content needed: "Read Operations"
Content needed: "Read Operations" - Key: ZOOKEEPER-170 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-170 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott We need the content which describes how to a client should read data from a zookeeper node. Ideally this would have pseudo code describing any lead-up (for example resource allocation, etc), a few lines of sample code in Java, and a few parallel lines in C. Any commentary would be highly appreciated -- anything about reading data that would not be obvious to a new ZooKeeper developer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-169) Content needed: "Connecting to ZooKeeper"
Content needed: "Connecting to ZooKeeper" - Key: ZOOKEEPER-169 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-169 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott We need the content which describes how to a client should connect to a zookeeper server. Ideally this would have pseudo code describing any lead-up (for example resource allocation, etc), a few lines of sample code in Java, and a few parallel lines in C. Any commentary would be highly appreciated. Stuff like, "You can open an unlimited number of ZooKeeper connections because..." or "Opening too many connections to ZooKeeper is not advisable because..." -- in short, anything that is not obvious to the new ZooKeeper developer. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-168) Programmer's Guide "Basic Operations" section is missing content
Programmer's Guide "Basic Operations" section is missing content Key: ZOOKEEPER-168 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-168 Project: Zookeeper Issue Type: Bug Components: documentation Reporter: Robbie Scott There is a chapter in the ZooKeeper Programmer's Guide called: "Building Blocks: A Guide to ZooKeeper Operations" that currently contains no content. The idea behind this section is document all the basic things you can do with the ZooKeeper API -- not every little detail, or even every call in the API, but the basics, like: how to connect to a server, how to read a node, how to write to a node, how to set a watch, etc. I will create a subtask for every section in this chapter. I don't mind writing up the these sections, if I can get the information, whether its' by phone, email, im, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-167) Content needed: "Troubleshooting"
Content needed: "Troubleshooting" - Key: ZOOKEEPER-167 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-167 Project: Zookeeper Issue Type: Sub-task Reporter: Robbie Scott We need the content / information / knowledge for the "Troubleshooting" subsection of the ZooKeeper Administrator's Guide. This is information about what to do when an existing deployment of ZooKeeper has problems. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-166) Content needed: "Logging"
Content needed: "Logging" - Key: ZOOKEEPER-166 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-166 Project: Zookeeper Issue Type: Sub-task Reporter: Robbie Scott Content/information needed on Logging, from the point of view of the ZooKeeper Administrator -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-163) Content needed: "Things to Consider: Strengths and Limitations"
Content needed: "Things to Consider: Strengths and Limitations" --- Key: ZOOKEEPER-163 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-163 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott I need content for the section "Things to Consider: ZooKeeper Strengths and Limitations" in the ZooKeeper admin guide. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-165) Content needed: "Monitoring"
Content needed: "Monitoring" Key: ZOOKEEPER-165 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-165 Project: Zookeeper Issue Type: Sub-task Components: documentation Reporter: Robbie Scott Content/information needed on how to Monitor a zooKeeper deployment. I think we can talk about jmx, etc -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-164) Content needed: "Administering"
Content needed: "Administering" --- Key: ZOOKEEPER-164 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-164 Project: Zookeeper Issue Type: Sub-task Reporter: Robbie Scott Content/Information needed on the day to day running, management, administering of a ZooKeeper deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-162) Content needed: Provisioning
Content needed: Provisioning Key: ZOOKEEPER-162 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-162 Project: Zookeeper Issue Type: Sub-task Reporter: Robbie Scott I need the content for the ZooKeeper Admin guide, for the section on "Provisioning" your zookeeper deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"
[ https://issues.apache.org/jira/browse/ZOOKEEPER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-161: --- Remaining Estimate: 8h (was: 0.13h) Original Estimate: 8h (was: 0.13h) > 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 >Reporter: Robbie Scott > 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] Updated: (ZOOKEEPER-160) Admin / Ops Guide Missing Content
[ https://issues.apache.org/jira/browse/ZOOKEEPER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Scott updated ZOOKEEPER-160: --- Remaining Estimate: (was: 32h) Original Estimate: (was: 32h) > Admin / Ops Guide Missing Content > - > > Key: ZOOKEEPER-160 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-160 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Reporter: Robbie Scott > > I'm adding new sections to the ZooKeeper Admin guide, but I don't have the > content to fill them out. These sections are: > - Designing a ZooKeeper Deployment > - Provisioning > - Things to Consider: ZooKeeper Strengths and Limitations > - Administering > - Monitoring > - Logging > - Troubleshooting > I'll add a subtask for each section. > Note: If the area experts prefer, I can conduct a phone interview or email > conversation or IM with them on the topic, and then write up the section so > they don't have to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-161) 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 Reporter: Robbie Scott 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] Created: (ZOOKEEPER-160) Admin / Ops Guide Missing Content
Admin / Ops Guide Missing Content - Key: ZOOKEEPER-160 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-160 Project: Zookeeper Issue Type: Bug Components: documentation Reporter: Robbie Scott I'm adding new sections to the ZooKeeper Admin guide, but I don't have the content to fill them out. These sections are: - Designing a ZooKeeper Deployment - Provisioning - Things to Consider: ZooKeeper Strengths and Limitations - Administering - Monitoring - Logging - Troubleshooting I'll add a subtask for each section. Note: If the area experts prefer, I can conduct a phone interview or email conversation or IM with them on the topic, and then write up the section so they don't have to. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-159) Cover two corner cases of leader election
Cover two corner cases of leader election - Key: ZOOKEEPER-159 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-159 Project: Zookeeper Issue Type: Bug Components: leaderElection Reporter: Flavio Paiva Junqueira Fix For: 3.0.0 Attachments: ZOOKEEPER-159.patch In the default implementation of leader election, there are two undesirable cases that need to be covered: 1- If there is a leader elected and this leader is supported by at least quorum of peers, then it can happen that one peer disconnects from the leader, and initiates a new leader election. As it is a new leader election, we increment the logical clock of this peer, and according to the current implementation, this peer won't accept any vote from a peer with a lower LE turn (corresponds to the value of the logical clock of the voting peer). The attached patch corrects this problem by allowing a peer to go back to a previous epoch in the case a majority votes for a leader, and the peer also receives a vote from the leader. This feature allows a peer to correct a false suspicion of the current leader; 2- If a peer advances to a new turn before others, then it may end up voting for a peer that either does not have the highest server id or the the highest zxid. The attached patch fixes this problem by resetting the vote a peer when it updates its logical clock upon receiving a notification with a higher turn value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-159) Cover two corner cases of leader election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-159: - Status: Patch Available (was: Open) > Cover two corner cases of leader election > - > > Key: ZOOKEEPER-159 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-159 > Project: Zookeeper > Issue Type: Bug > Components: leaderElection >Reporter: Flavio Paiva Junqueira > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-159.patch > > > In the default implementation of leader election, there are two undesirable > cases that need to be covered: > 1- If there is a leader elected and this leader is supported by at least > quorum of peers, then it can happen that one peer disconnects from the > leader, and initiates a new leader election. As it is a new leader election, > we increment the logical clock of this peer, and according to the current > implementation, this peer won't accept any vote from a peer with a lower LE > turn (corresponds to the value of the logical clock of the voting peer). The > attached patch corrects this problem by allowing a peer to go back to a > previous epoch in the case a majority votes for a leader, and the peer also > receives a vote from the leader. This feature allows a peer to correct a > false suspicion of the current leader; > 2- If a peer advances to a new turn before others, then it may end up voting > for a peer that either does not have the highest server id or the the highest > zxid. The attached patch fixes this problem by resetting the vote a peer when > it updates its logical clock upon receiving a notification with a higher turn > value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-159) Cover two corner cases of leader election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-159: - Attachment: ZOOKEEPER-159.patch This patch passes the unit tests and my manual tests and benchmarks. > Cover two corner cases of leader election > - > > Key: ZOOKEEPER-159 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-159 > Project: Zookeeper > Issue Type: Bug > Components: leaderElection >Reporter: Flavio Paiva Junqueira > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-159.patch > > > In the default implementation of leader election, there are two undesirable > cases that need to be covered: > 1- If there is a leader elected and this leader is supported by at least > quorum of peers, then it can happen that one peer disconnects from the > leader, and initiates a new leader election. As it is a new leader election, > we increment the logical clock of this peer, and according to the current > implementation, this peer won't accept any vote from a peer with a lower LE > turn (corresponds to the value of the logical clock of the voting peer). The > attached patch corrects this problem by allowing a peer to go back to a > previous epoch in the case a majority votes for a leader, and the peer also > receives a vote from the leader. This feature allows a peer to correct a > false suspicion of the current leader; > 2- If a peer advances to a new turn before others, then it may end up voting > for a peer that either does not have the highest server id or the the highest > zxid. The attached patch fixes this problem by resetting the vote a peer when > it updates its logical clock upon receiving a notification with a higher turn > value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
