hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3077) Quorum-based protocol for reading and writing edit logs
Date Thu, 19 Jul 2012 19:45:36 GMT

     [ 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.txt

I've been testing this on a couple different clusters locally and mostly working well, modulo
the existing cases where there are TODOs. There's more work to do, but keeping this patch
mostly as-is so it can be reviewed and checked into a branch.

This new rev is a fairly small delta from the previous one:

    - Fix bin/hdfs script - elif vs if typo in previous rev
    - Remove an empty format() stub in FSEditLog (added in a previous rev, but unused)
    - revert a spurious FileSystem change which should not be in 3077
    - Add TODO about close() hanging when remote side is down (noticed while manual testing)
    - improve TODO AssertionError for empty logs to include the path of the empty log
    - Add a TODO about null segments during recovery, a case which occurred during manual
testing

                
> 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, hdfs-3077.txt, hdfs-3077.txt,
hdfs-3077.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

        

Mime
View raw message