[
https://issues.apache.org/jira/browse/HDFS-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229196#comment-13229196
]
Suresh Srinivas commented on HDFS-3077:
---------------------------------------
Todd, as indicated yesterday, I have created HDFS-3092, to contribute the early
prototype that uses journal protocol on the standby. This could be evolved to
the stand alone daemon you mention in first part of your description.
I agree with most of the description in this jira, as we were thinking along
the same lines. However, I am not sure I understand the benefits of
implementing ZAB are. My preferences is to keep editlog path as simple as
possible. Currently we have multiple copies of edits. Chosing the right one is
an issue. That could be solved in simple ways - instead of adding complexity to
this layer.
> Quorum-based protocol for reading and writing edit logs
> -------------------------------------------------------
>
> Key: HDFS-3077
> URL: https://issues.apache.org/jira/browse/HDFS-3077
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: ha, name-node
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> Currently, one of the weak points of the HA design is that it relies on
> shared storage such as an NFS filer for the shared edit log. One alternative
> that has been proposed is to depend on BookKeeper, a ZooKeeper subproject
> which provides a highly available replicated edit log on commodity hardware.
> This JIRA is to implement another alternative, based on a quorum commit
> protocol, integrated more tightly in HDFS and with the requirements driven
> only by HDFS's needs rather than more generic use cases. More details to
> follow.
--
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
