HDFS-8544. Incorrect port specified in HFTP Guide document in branch-2. (Contributed by Brahma Reddy Battula)

This commit is contained in:
Yongjun Zhang 2015-06-15 21:45:30 -07:00
parent ff6d5f2ee7
commit b1d3ed02c1
2 changed files with 4 additions and 1 deletions

View File

@ -682,6 +682,9 @@ Release 2.7.1 - UNRELEASED
HDFS-8576. Lease recovery should return true if the lease can be released HDFS-8576. Lease recovery should return true if the lease can be released
and the file can be closed. (J.Andreina via szetszwo) and the file can be closed. (J.Andreina via szetszwo)
HDFS-8544. Incorrect port specified in HFTP Guide document in branch-2.
(Brahma Reddy Battula via Yongjun Zhang)
Release 2.7.0 - 2015-04-20 Release 2.7.0 - 2015-04-20
INCOMPATIBLE CHANGES INCOMPATIBLE CHANGES

View File

@ -33,7 +33,7 @@ state.
HFTP is primarily useful if you have multiple HDFS clusters with HFTP is primarily useful if you have multiple HDFS clusters with
different versions and you need to move data from one to another. HFTP different versions and you need to move data from one to another. HFTP
is wire-compatible even between different versions of HDFS. For is wire-compatible even between different versions of HDFS. For
example, you can do things like: `hadoop distcp -i hftp://sourceFS:50070/src hdfs://destFS:50070/dest`. example, you can do things like: `hadoop distcp -i hftp://sourceFS:50070/src hdfs://destFS:8020/dest`.
Note that HFTP is read-only so the destination must be an HDFS filesystem. Note that HFTP is read-only so the destination must be an HDFS filesystem.
(Also, in this example, the distcp should be run using the configuraton of (Also, in this example, the distcp should be run using the configuraton of
the new filesystem.) the new filesystem.)