[
https://issues.apache.org/jira/browse/HBASE-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Trezzo updated HBASE-6168:
--------------------------------
Attachment: HBASE-6168v3.patch
Thanks Enis for the comment.
- The peer name does not have to be an integer, you are totally right. I have
removed the comment about it being an integer.
- I left out the failover lock stuff for simplicity of the explanation. I was
thinking about doing a section specifically on what happens to zookeeper state
in failover scenarios, but I decided to hold off because I think it might
change in the near future due to HBASE-2611. :-)
Attached is another patch.
Chris
> [replication] Add replication zookeeper state documentation to
> replication.html
> -------------------------------------------------------------------------------
>
> Key: HBASE-6168
> URL: https://issues.apache.org/jira/browse/HBASE-6168
> Project: HBase
> Issue Type: Improvement
> Components: documentation, replication
> Affects Versions: 0.96.0
> Reporter: Chris Trezzo
> Assignee: Chris Trezzo
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-6168.patch, HBASE-6168v2.patch, HBASE-6168v3.patch
>
>
> Add a detailed explanation about the zookeeper state that HBase replication
> maintains.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira