HDFS-6704. Merge r1612613 from trunk.

git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2@1612615 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jing Zhao 2014-07-22 17:12:26 +00:00
parent 73d109304d
commit 976af1d50a
2 changed files with 5 additions and 2 deletions

View File

@ -96,6 +96,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

View File

@ -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.