[
https://issues.apache.org/jira/browse/HDFS-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-3077:
------------------------------
Attachment: hdfs-3077-branch-2.txt
This patch consists of the full merge for branch-2. There were a few conflicts
here and there but nothing too major. A few notes I made while doing the
backport:
- Incorporates change from HDFS-4121 in trunk to add proto namespace
declaration to QJournalProtocol.proto
- change the pom.xml to include QJournalProtocol (part of HDFS-4041 from
trunk)
This backport depends on HDFS-3049 and HDFS-3571 backports - I posted patches
for those on the respective JIRAs. I ran the tests in the qjournal package and
they passed.
> 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, namenode
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 3.0.0, QuorumJournalManager (HDFS-3077)
>
> Attachments: hdfs-3077-branch-2.txt, hdfs-3077-partial.txt,
> hdfs-3077-test-merge.txt, hdfs-3077.txt, hdfs-3077.txt, hdfs-3077.txt,
> hdfs-3077.txt, hdfs-3077.txt, hdfs-3077.txt, hdfs-3077.txt,
> qjournal-design.pdf, qjournal-design.pdf, qjournal-design.pdf,
> qjournal-design.pdf, qjournal-design.pdf, qjournal-design.pdf,
> qjournal-design.tex, qjournal-design.tex
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
