[
https://issues.apache.org/jira/browse/HDFS-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401956#comment-13401956
]
Suresh Srinivas commented on HDFS-3077:
---------------------------------------
bq. I would have liked to use the code exactly as it was, but the differences
in design made it too difficult to try to reconcile, and I ended up
copy-pasting and modifying rather than patching against that branch.
Todd, 3092 focused mainly on the server side. Some of the client side, we
abandoned given the work in 3077. I want to understand how the changes can be
reconciled with 3092. Currently BackupNode is being updated to used the
JournalService. Once this is done, we were planning to merge 3092 into trunk.
How should we proceed to merge 3077 and 3092 to trunk?
bq. Andy asked me to post a link to the corresponding github branch:
https://github.com/toddlipcon/hadoop-common/commits/qjm-patchseries
Is code review going to be based off of this or code changes into a branch on
Apache Hadoop code base?
> 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
> Attachments: hdfs-3077-partial.txt, hdfs-3077.txt,
> qjournal-design.pdf, qjournal-design.pdf
>
>
> 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
