Apache
/
hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HDFS-8222. Remove usage of "dfsadmin -upgradeProgress" from document which is no longer supported. Contributed by J.Andreina. 

(cherry picked from commit fd605997ee)
This commit is contained in:
Akira Ajisaka 2015-05-08 16:25:56 +09:00
parent 1f78502416
commit 143c9a8ff2
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
View File

@ -342,6 +342,9 @@ Release 2.8.0 - UNRELEASED
HDFS-7998. HDFS Federation : Command mentioned to add a NN to existing
federated cluster is wrong (Ajith S via vinayakumarb)
HDFS-8222. Remove usage of "dfsadmin -upgradeProgress" from document which
is no longer supported. (J.Andreina via aajisaka)
Release 2.7.1 - UNRELEASED
INCOMPATIBLE CHANGES

3
hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsUserGuide.md
View File

@ -302,8 +302,7 @@ Upgrade and Rollback
When Hadoop is upgraded on an existing cluster, as with any software upgrade, it is possible there are new bugs or incompatible changes that affect existing applications and were not discovered earlier. In any non-trivial HDFS installation, it is not an option to loose any data, let alone to restart HDFS from scratch. HDFS allows administrators to go back to earlier version of Hadoop and rollback the cluster to the state it was in before the upgrade. HDFS upgrade is described in more detail in [Hadoop Upgrade](http://wiki.apache.org/hadoop/Hadoop_Upgrade) Wiki page. HDFS can have one such backup at a time. Before upgrading, administrators need to remove existing backup using bin/hadoop dfsadmin `-finalizeUpgrade` command. The following briefly describes the typical upgrade procedure:
* Before upgrading Hadoop software, finalize if there an existing
backup. `dfsadmin -upgradeProgress` status can tell if the cluster
needs to be finalized.
backup.
* Stop the cluster and distribute new version of Hadoop.