HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document. Contributed by Akira AJISAKA.
git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/trunk@1612613 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
9c062e03d1
commit
0c72ca9e7a
@ -348,6 +348,9 @@ Release 2.6.0 - UNRELEASED
|
|||||||
HDFS-6667. In HDFS HA mode, Distcp/SLive with webhdfs on secure cluster fails
|
HDFS-6667. In HDFS HA mode, Distcp/SLive with webhdfs on secure cluster fails
|
||||||
with Client cannot authenticate via:[TOKEN, KERBEROS] error. (jing9)
|
with Client cannot authenticate via:[TOKEN, KERBEROS] error. (jing9)
|
||||||
|
|
||||||
|
HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document.
|
||||||
|
(Akira AJISAKA via jing9)
|
||||||
|
|
||||||
Release 2.5.0 - UNRELEASED
|
Release 2.5.0 - UNRELEASED
|
||||||
|
|
||||||
INCOMPATIBLE CHANGES
|
INCOMPATIBLE CHANGES
|
||||||
|
@ -416,8 +416,8 @@ HDFS High Availability Using the Quorum Journal Manager
|
|||||||
|
|
||||||
After all of the necessary configuration options have been set, you must
|
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
|
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
|
can be done by running the command "<hadoop-daemon.sh start journalnode>" and
|
||||||
for the daemon to start on each of the relevant machines.
|
waiting for the daemon to start on each of the relevant machines.
|
||||||
|
|
||||||
Once the JournalNodes have been started, one must initially synchronize the
|
Once the JournalNodes have been started, one must initially synchronize the
|
||||||
two HA NameNodes' on-disk metadata.
|
two HA NameNodes' on-disk metadata.
|
||||||
|
Loading…
Reference in New Issue
Block a user