[jira] [Updated] (HDFS-8914) Document HA support in the HDFS HdfsDesign.md

["Akira AJISAKA (JIRA)" <ji...@apache.org>]

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

Akira AJISAKA updated HDFS-8914:
--------------------------------
         Due Date:     (was: 20/Aug/15)
         Priority: Major  (was: Trivial)
    Fix Version/s: 2.7.3

I think the fix is very important because users probably read this document at first and may misunderstand that NameNode is SPOF. Cherry-picked this to branch-2.7.

> Document HA support in the HDFS HdfsDesign.md
> ---------------------------------------------
>
>                 Key: HDFS-8914
>                 URL: https://issues.apache.org/jira/browse/HDFS-8914
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.7.1
>         Environment: Documentation page in live
>            Reporter: Ravindra Babu
>            Assignee: Lars Francke
>             Fix For: 2.8.0, 2.7.3
>
>         Attachments: HDFS-8914.1.patch, HDFS-8914.2.patch
>
>
> Please refer to these two links and correct one of them.
> http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html
> The NameNode machine is a single point of failure for an HDFS cluster. If the NameNode machine fails, manual intervention is necessary. Currently, automatic restart and failover of the NameNode software to another machine is not supported.
> http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html
> The HDFS High Availability feature addresses the above problems by providing the option of running two redundant NameNodes in the same cluster in an Active/Passive configuration with a hot standby. This allows a fast failover to a new NameNode in the case that a machine crashes, or a graceful administrator-initiated failover for the purpose of planned maintenance.
> Please update hdfsDesign article with same facts to avoid confusion in Reader's mind..



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)