[
https://issues.apache.org/jira/browse/HDFS-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066431#comment-15066431
]
Akira AJISAKA commented on HDFS-8914:
-------------------------------------
bq. How to know which all unit tests have been failed
Failed tests are listed in the following link, but the link will be expired in
a few weeks. (This link is expired.)
bq. FAILURE: Integrated in Hadoop-Hdfs-trunk #2567 (See
https://builds.apache.org/job/Hadoop-Hdfs-trunk/2567/)
bq. and how to address them?
Usually the test failures have been already reported in jira. You can search
the issue and fix the test. If you can't find the issue, you can create a issue
to fix the the failing test.
bq. Is there a way to get it deployed without addressing these failures?
The tests are executed after the patch is committed, so the patch is applied to
trunk/branch-2/... if the tests fail or not.
> 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)
