From 91b97c21c9271629dae7515a6a58c35d13b777ff Mon Sep 17 00:00:00 2001
From: Akira Ajisaka
Date: Fri, 24 Apr 2015 20:32:26 +0900
Subject: [PATCH] HDFS-8110. Remove unsupported 'hdfs namenode -rollingUpgrade
downgrade' from document. Contributed by J.Andreina.
---
hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt | 3 +++
.../src/site/xdoc/HdfsRollingUpgrade.xml | 26 +++----------------
2 files changed, 6 insertions(+), 23 deletions(-)
diff --git a/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt b/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
index b442bad4ce9..56f8ec361e0 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
+++ b/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
@@ -315,6 +315,9 @@ Trunk (Unreleased)
HDFS-4681. TestBlocksWithNotEnoughRacks#testCorruptBlockRereplicatedAcrossRacks
fails using IBM java (Ayappan via aw)
+ HDFS-8110. Remove unsupported 'hdfs namenode -rollingUpgrade downgrade'
+ from document. (J.Andreina via aajisaka)
+
Release 2.8.0 - UNRELEASED
INCOMPATIBLE CHANGES
diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/site/xdoc/HdfsRollingUpgrade.xml b/hadoop-hdfs-project/hadoop-hdfs/src/site/xdoc/HdfsRollingUpgrade.xml
index 1c3dc6092bf..f0b0ccf0df0 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/src/site/xdoc/HdfsRollingUpgrade.xml
+++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/xdoc/HdfsRollingUpgrade.xml
@@ -190,14 +190,12 @@
only if both the namenode layout version and the datenode layout version
are not changed between these two releases.
-
-
In a HA cluster,
when a rolling upgrade from an old software release to a new software release is in progress,
it is possible to downgrade, in a rolling fashion, the upgraded machines back to the old software release.
Same as before, suppose NN1 and NN2 are respectively in active and standby states.
- Below are the steps for rolling downgrade:
+ Below are the steps for rolling downgrade without downtime:
- Downgrade DNs
@@ -214,16 +212,12 @@
- Downgrade Active and Standby NNs
- Shutdown and downgrade NN2.
- - Start NN2 as standby normally. (Note that it is incorrect to use the
- "
-rollingUpgrade downgrade
"
- option here.)
+ - Start NN2 as standby normally.
- Failover from NN1 to NN2
so that NN2 becomes active and NN1 becomes standby.
- Shutdown and upgrade NN1.
- - Start NN1 as standby normally. (Note that it is incorrect to use the
- "
-rollingUpgrade downgrade
"
- option here.)
+ - Start NN1 as standby normally.
- Finalize Rolling Downgrade
@@ -236,20 +230,6 @@
since protocols may be changed in a backward compatible manner but not forward compatible,
i.e. old datanodes can talk to the new namenodes but not vice versa.
-
-
-
- Administrator may choose to first shutdown the cluster and then downgrade it.
- The following are the steps:
-
-
- - Shutdown all NNs and DNs.
- - Restore the pre-upgrade release in all machines.
- - Start NNs with the
- "
-rollingUpgrade downgrade
" option.
- - Start DNs normally.
-
-