hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravindra Babu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8914) Documentation conflict regarding fail-over of Namenode
Date Mon, 19 Oct 2015 03:30:05 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962799#comment-14962799
] 

Ravindra Babu commented on HDFS-8914:
-------------------------------------

Hi, Please deploy this patch as early as possible to avoid confusion in reader's mind. Without
this patch, readers of HDFS design article will think that HDFS name node is single point
of failure in the system even though it's not a single point of failure. 

> Documentation conflict regarding fail-over of Namenode
> ------------------------------------------------------
>
>                 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
>            Priority: Trivial
>         Attachments: HDFS-8914.1.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 keep one right version regarding failover statements.



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

Mime
View raw message