From 3f1a341454b0fd3c7da6e3f4a188f5a2ce6c1ae1 Mon Sep 17 00:00:00 2001 From: Guanghao Zhang Date: Thu, 28 Feb 2019 17:45:39 +0800 Subject: [PATCH] HBASE-21970 Document that how to upgrade from 2.0 or 2.1 to 2.2+ --- src/main/asciidoc/_chapters/upgrading.adoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/src/main/asciidoc/_chapters/upgrading.adoc b/src/main/asciidoc/_chapters/upgrading.adoc index da0dac0..ad8924a 100644 --- a/src/main/asciidoc/_chapters/upgrading.adoc +++ b/src/main/asciidoc/_chapters/upgrading.adoc @@ -314,6 +314,20 @@ Quitting... == Upgrade Paths +[[upgrade 2.2]] +=== Upgrade from 2.0 or 2.1 to 2.2+ + +HBase 2.2+ uses a new Procedure form assiging/unassigning/moving Regions. It does not process HBase 2.1 and 2.0's Unassign/Assign Procedure types. Upgrade requires that we first drain the Master Procedure Store of old style Procedures before starting the new 2.2 Master. So you need to make sure that before you killing the old version (2.0 or 2.1) Master, there is no region in transactions. And once the new version (2.2+) Master is up, you can rolling upgrade RegionServers one by one. + +And there is a more safer way if you are running 2.1.1+ or 2.0.3+ cluster. It need four steps to upgrade Master. + +. Shutdown both active and standby Masters (Your cluster will continue to server reads and writes without interruption). +. Set the property hbase.procedure.upgrade-to-2-2 to true in hbase-site.xml for the Master, and start only one Master, still using the 2.1.1+ (or 2.0.3+) version. +. Wait until the Master quits. Confirm that there is a 'READY TO ROLLING UPGRADE' message in the Master log as the cause of the shutdown. The Procedure Store is now empty. +. Start new Masters with the new 2.2+ version. + +Then you can rolling upgrade RegionServers one by one. See link:https://issues.apache.org/jira/browse/HBASE-21075[HBASE-21075] for more details. + [[upgrade2.0]] === Upgrading from 1.x to 2.x -- 2.7.4