[
https://issues.apache.org/jira/browse/HDFS-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravindra Babu updated HDFS-8914:
--------------------------------
Description:
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..
was:
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.
> 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 update hdfsDesign article with same facts to avoid confusion in
> Reader's mind..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
