hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject git commit: HBASE-11164 Document and test rolling updates from 0.98 -> 1.0; Add note on why can't go from 0.96 to 1.0 and define what rolling upgrade is
Date Fri, 24 Oct 2014 03:48:43 GMT
Repository: hbase
Updated Branches:
  refs/heads/master 96f84594e -> eae0f202c


HBASE-11164 Document and test rolling updates from 0.98 -> 1.0; Add note on why can't go
from 0.96 to 1.0 and define what rolling upgrade is


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

Branch: refs/heads/master
Commit: eae0f202cec535bfa0fc8dff1401b7afbe11f33f
Parents: 96f8459
Author: stack <stack@apache.org>
Authored: Thu Oct 23 20:48:34 2014 -0700
Committer: stack <stack@apache.org>
Committed: Thu Oct 23 20:48:34 2014 -0700

----------------------------------------------------------------------
 src/main/docbkx/upgrading.xml | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/eae0f202/src/main/docbkx/upgrading.xml
----------------------------------------------------------------------
diff --git a/src/main/docbkx/upgrading.xml b/src/main/docbkx/upgrading.xml
index d45a22e..5f84364 100644
--- a/src/main/docbkx/upgrading.xml
+++ b/src/main/docbkx/upgrading.xml
@@ -84,6 +84,15 @@
                 from 0.94.5 by doing a rolling upgrade across the cluster replacing the 0.94.5
                 binary with a 0.94.6 binary. </para>
         </section>
+        <section xml:id="rolling.upgrade">
+          <title><firstterm>Rolling Upgrades</firstterm></title>
+          <para>A rolling upgrade is the process by which you update the servers
+            in your cluster a server at a time.  Coarsely, you do a graceful stop of the
server
+            update the software and then restart.  You do this for each server in the cluster.
+            Usually you upgrade the Master first and then the regionservers.
+            See <xlink href="rolling" /> for tools that can help use the rolling upgrade
process:
+          e.g. install the new software and configs and then do a rolling restart to come
up on it.</para>
+        </section>
     </section>
     <section xml:id="upgrade1.0">
         <title>Upgrading from 0.98.x to 1.0.x</title>
@@ -120,6 +129,12 @@
         </section>
         <section xml:id="upgrade1.0.rolling.upgrade">
           <title>Rolling upgrade from 0.98.x to HBase 1.0.0</title>
+          <note><title>From 0.96.x to 1.0.0</title>
+            <para>You cannot do a <xlink href="rolling.upgrade" /> from 0.96.x
to 1.0.0 without
+              first doing a rolling upgrade to 0.98.x. See comment in
+              <link xlink:href="https://issues.apache.org/jira/browse/HBASE-11164?focusedCommentId=14182330&amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14182330">HBASE-11164
Document and test rolling updates from 0.98 -> 1.0</link> for the why.
+            </para>
+          </note>
           <para>TODO</para>
         </section>
         <section xml:id="upgrade1.0.from.0.94">


Mime
View raw message