[
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066144#comment-14066144
]
Hadoop QA commented on HDFS-6704:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12656444/HDFS-6704.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7380//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7380//console
This message is automatically generated.
> Fix the command to launch JournalNode in HDFS-HA document
> ---------------------------------------------------------
>
> Key: HDFS-6704
> URL: https://issues.apache.org/jira/browse/HDFS-6704
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.4.0
> Reporter: Akira AJISAKA
> Assignee: Akira AJISAKA
> Priority: Minor
> Labels: newbie
> Attachments: HDFS-6704.patch
>
>
> In HDFSHighAvailabilityWithQJM.html,
> {code}
> After all of the necessary configuration options have been set, you must
> start the JournalNode daemons on the set of machines where they will run.
> This can be done by running the command "hdfs-daemon.sh journalnode" and
> waiting for the daemon to start on each of the relevant machines.
> {code}
> hdfs-daemon.sh should be hadoop-daemon.sh since hdfs-daemon.sh does not exist.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
