hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1975) HA: Support for sharing the namenode state from active to standby.
Date Tue, 15 Nov 2011 07:37:51 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aaron T. Myers updated HDFS-1975:
---------------------------------

    Attachment: HDFS-1975-HDFS-1623.patch

Here's an updated version of the previous patch provided by Jitendra. It does the following
things:

# Rebased on current HDFS-1623 branch.
# Adds infrastructure to MiniDFSCluster to be able to start HA NNs.
# Adds a test based roughly on Todd's earlier test.
# Fixes up a few corner cases.
# Should address all of Todd's feedback.

Todd, could you please take a look at this? The one piece of feedback I didn't take was changing
sharedEditsDirs to sharedEditsUris, since doing so would be inconsistent with all the other
places in the code where we refer to those collections as "dirs."
                
> HA: Support for sharing the namenode state from active to standby.
> ------------------------------------------------------------------
>
>                 Key: HDFS-1975
>                 URL: https://issues.apache.org/jira/browse/HDFS-1975
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>            Reporter: Suresh Srinivas
>            Assignee: Jitendra Nath Pandey
>         Attachments: HDFS-1975-HA.2.patch, HDFS-1975-HA.patch, HDFS-1975-HDFS-1623.patch,
hdfs-1975.txt, hdfs-1975.txt
>
>
> To enable hot standby namenode, the standby node must have current information for -
namenode state (image + edits) and block location information. This jira addresses keeping
the namenode state current in the standby node. To do this, the proposed solution in this
jira is to use a shared storage to store the namenode state. 
> Note one could also build an alternative solution by augmenting the backup node. A seperate
jira could explore this.

--
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