[
https://issues.apache.org/jira/browse/HDFS-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071732#comment-14071732
]
Hudson commented on HDFS-6704:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #1813 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1813/])
HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document.
Contributed by Akira AJISAKA. (jing9:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1612613)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/site/apt/HDFSHighAvailabilityWithQJM.apt.vm
> 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
> Fix For: 2.6.0
>
> Attachments: HDFS-6704.2.patch, 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)