hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aajis...@apache.org
Subject hadoop git commit: HDFS-8110. Remove unsupported 'hdfs namenode -rollingUpgrade downgrade' from document. Contributed by J.Andreina.
Date Fri, 24 Apr 2015 11:34:04 GMT
Repository: hadoop
Updated Branches:
  refs/heads/trunk c8d72907f -> 91b97c21c


HDFS-8110. Remove unsupported 'hdfs namenode -rollingUpgrade downgrade' from document. Contributed
by J.Andreina.


Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo
Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/91b97c21
Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/91b97c21
Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/91b97c21

Branch: refs/heads/trunk
Commit: 91b97c21c9271629dae7515a6a58c35d13b777ff
Parents: c8d7290
Author: Akira Ajisaka <aajisaka@apache.org>
Authored: Fri Apr 24 20:32:26 2015 +0900
Committer: Akira Ajisaka <aajisaka@apache.org>
Committed: Fri Apr 24 20:32:55 2015 +0900

----------------------------------------------------------------------
 hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt     |  3 +++
 .../src/site/xdoc/HdfsRollingUpgrade.xml        | 26 +++-----------------
 2 files changed, 6 insertions(+), 23 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/91b97c21/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
----------------------------------------------------------------------
diff --git a/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt b/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
index b442bad..56f8ec3 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

http://git-wip-us.apache.org/repos/asf/hadoop/blob/91b97c21/hadoop-hdfs-project/hadoop-hdfs/src/site/xdoc/HdfsRollingUpgrade.xml
----------------------------------------------------------------------
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 1c3dc60..f0b0ccf 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.
   </p>
-
-  <subsection name="Downgrade without Downtime" id="DowngradeWithoutDowntime">
   <p>
     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 <em>NN1</em> and <em>NN2</em> are respectively
in active and standby states.
-    Below are the steps for rolling downgrade:
+    Below are the steps for rolling downgrade without downtime:
   </p>
   <ol>
     <li>Downgrade <em>DNs</em><ol>
@@ -214,16 +212,12 @@
     </ol></li>
     <li>Downgrade Active and Standby <em>NNs</em><ol>
       <li>Shutdown and downgrade <em>NN2</em>.</li>
-      <li>Start <em>NN2</em> as standby normally. (Note that it is incorrect
to use the
-        "<a href="#namenode_-rollingUpgrade"><code>-rollingUpgrade downgrade</code></a>"
-        option here.)
+      <li>Start <em>NN2</em> as standby normally.
       </li>
       <li>Failover from <em>NN1</em> to <em>NN2</em>
         so that <em>NN2</em> becomes active and <em>NN1</em> becomes
standby.</li>
       <li>Shutdown and upgrade <em>NN1</em>.</li>
-      <li>Start <em>NN1</em> as standby normally. (Note that it is incorrect
to use the
-        "<a href="#namenode_-rollingUpgrade"><code>-rollingUpgrade downgrade</code></a>"
-        option here.)
+      <li>Start <em>NN1</em> as standby normally.
       </li>
     </ol></li>
     <li>Finalize Rolling Downgrade<ul>
@@ -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.
   </p>
-  </subsection>
-  <subsection name="Downgrade with Downtime" id="DowngradeWithDowntime">
-  <p>
-    Administrator may choose to first shutdown the cluster and then downgrade it.
-    The following are the steps:
-  </p>
-  <ol>
-      <li>Shutdown all <em>NNs</em> and <em>DNs</em>.</li>
-      <li>Restore the pre-upgrade release in all machines.</li>
-      <li>Start <em>NNs</em> with the 
-        "<a href="#namenode_-rollingUpgrade"><code>-rollingUpgrade downgrade</code></a>"
option.</li>
-      <li>Start <em>DNs</em> normally.</li>
-  </ol>
-  </subsection>
   </section>
 
   <section name="Rollback" id="Rollback">


Mime
View raw message