Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 19 Jul 2014 01:54:38 +0000 (UTC)
From: "Akira AJISAKA (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12728129.1405658873087.1164.1405734878738@arcas>
In-Reply-To: <JIRA.12728129.1405658873087@arcas>
References: <JIRA.12728129.1405658873087@arcas>
Subject: [jira] [Commented] (HDFS-6704) Fix the command to launch
 JournalNode in HDFS-HA document
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Akira AJISAKA commented on HDFS-6704:
-------------------------------------

[~jingzhao], you are right. I'll update the patch shortly.

> 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)