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

Todd Lipcon updated HDFS-1975:
------------------------------

    Attachment: HDFS-1975-HDFS-1623.patch

Before committing I ran the rest of the edit-log tests and discovered a couple 
small issues. This patch has the following fixes:

    - fix TestEditLog to init journals for write to fix failing test cases
    - fix FSNamesystem to not use /tmp/hadoop-name as a default shared edits 
directory (fixes a failing TestEditLog case)
    - add shared edits dirs to hdfs-default.xml
    - fix MiniDFSCluster to not fail if running HA tests on a clean build dir 
(Files.deleteRecursively was failing if the dir didn't exist)
    - remove empty diff in HAUtil
    - rebase on new tip of branch

Since the above changes are pretty simple I'll commit under Eli's +1 tomorrow 
morning .
                
> 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-HDFS-1623.patch, 
> HDFS-1975-HDFS-1623.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

        

Reply via email to