This is an automated email from the ASF dual-hosted git repository.
bharathv pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase.git
The following commit(s) were added to refs/heads/master by this push:
new 51ed95c HBASE-26071: Document HBASE-26021 and upgrade considerations
for 1.7.0/1.7.1 (#3469)
51ed95c is described below
commit 51ed95c0cb07df67332b28eafdba691b80b67f73
Author: Bharath Vissapragada <[email protected]>
AuthorDate: Thu Jul 22 19:30:30 2021 -0700
HBASE-26071: Document HBASE-26021 and upgrade considerations for
1.7.0/1.7.1 (#3469)
Signed-off-by: Viraj Jasani <[email protected]>
Signed-off-by: Reid Chan <[email protected]>
---
src/main/asciidoc/_chapters/upgrading.adoc | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/src/main/asciidoc/_chapters/upgrading.adoc
b/src/main/asciidoc/_chapters/upgrading.adoc
index 04a9690..1064130 100644
--- a/src/main/asciidoc/_chapters/upgrading.adoc
+++ b/src/main/asciidoc/_chapters/upgrading.adoc
@@ -128,6 +128,13 @@ Previously, we tried to maintain dependency compatibility
for the underly Hadoop
|Operational Compatibility | N |N |Y
|===
+[IMPORTANT]
+======
+HBase 1.7.0 release violated client-server wire compatibility guarantees and
was subsequently
+withdrawn after the incompatibilities were reported and fixed in 1.7.1. If you
are considering an
+upgrade to 1.7.x line, see <<upgrade1.7.x>>.
+======
+
[[hbase.client.api.surface]]
==== HBase API Surface
@@ -799,6 +806,21 @@ To upgrade an existing HBase 1.x cluster, you should:
* Upgrade RegionServers
* (Eventually) Upgrade Clients
+[[upgrade1.7.x]]
+=== Upgrading to 1.7.1+
+HBase release 1.7.0 introduced an incompatible table metadata serialization
format that broke the
+minor release compatibility guarantees. The issue was reported in
https://issues.apache.org/jira/browse/HBASE-26021[HBASE-26021] and the
problematic serialization patch was reverted in
+HBase 1.7.1. Some important notes about 1.7.x upgrades below.
+
+* If you are considering an upgrade to 1.7.x version, skip 1.7.0 completely
and upgrade to 1.7.1+
+version. 1.7.0 was withdrawn and removed from the Apache sites.
+* If you already installed a 1.7.0 cluster from scratch and are looking to
migrate to 1.7.1+, you
+cannot follow the regular rolling upgrade procedures due to broken
compatibility contracts.
+Instead shutdown the cluster and reboot with 1.7.1+ binaries. Newer versions
detect any existing
+tables with incompatible serialization and rewrite them using the correct
format at bootstrap.
+* If you are already on 1.7.1+ version, everything is good and no additional
steps need to be
+performed.
+
[[upgrade1.4]]
=== Upgrading from pre-1.4 to 1.4+
