Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-24488 Update docs re: ZooKeeper compatibility of 2.3.x release (#1827) 

Add a note to the 2.3 upgrade section regarding the ZooKeeper version
bump and include a link off to ZooKeeper's FAQ.

Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: Jan Hentschel <janh@apache.org>
Signed-off-by: Viraj Jasani <vjasani@apache.org>
This commit is contained in:
Nick Dimiduk 2020-06-02 09:42:19 -07:00 committed by GitHub
parent e5345b3a7c
commit a8b3cad6c5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/main/asciidoc/_chapters/configuration.adoc
View File

@ -324,7 +324,9 @@ See also <<casestudies.max.transfer.threads,casestudies.max.transfer.threads>> a
[[zookeeper.requirements]] [[zookeeper.requirements]]
=== ZooKeeper Requirements === ZooKeeper Requirements
ZooKeeper 3.4.x is required. An Apache ZooKeeper quorum is required. The exact version depends on your version of HBase, though
the minimum ZooKeeper version is 3.4.x due to the `useMulti` feature made default in 1.0.0
(see https://issues.apache.org/jira/browse/HBASE-16598[HBASE-16598]).
[[standalone_dist]] [[standalone_dist]]
== HBase run modes: Standalone and Distributed == HBase run modes: Standalone and Distributed

14
src/main/asciidoc/_chapters/upgrading.adoc
View File

@ -324,11 +324,21 @@ The RegionServer Grouping feature has been reimplemented. See section
There is no special consideration upgrading to hbase-2.3.x from earlier versions. From 2.2.x, it should be There is no special consideration upgrading to hbase-2.3.x from earlier versions. From 2.2.x, it should be
rolling upgradeable. From 2.1.x or 2.0.x, you will need to clear the <<upgrade2.2>> hurdle first. rolling upgradeable. From 2.1.x or 2.0.x, you will need to clear the <<upgrade2.2>> hurdle first.
[[in-master-procedure-store-region]] [[upgrade2.3_zookeeper]]
==== Upgraded ZooKeeper Dependency Version
Our dependency on Apache ZooKeeper has been upgraded to 3.5.7
(https://issues.apache.org/jira/browse/HBASE-24132[HBASE-24132]), as 3.4.x is EOL. The newer 3.5.x
client is compatible with the older 3.4.x server. However, if you're using HBase in stand-alone
mode and perform an in-place upgrade, there are some upgrade steps
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ[documented by the ZooKeeper community].
This doesn't impact a production deployment, but would impact a developer's local environment.
[[upgrade2.3_in-master-procedure-store-region]]
==== New In-Master Procedure Store ==== New In-Master Procedure Store
Of note, HBase 2.3.0 changes the in-Master Procedure Store implementation. It was a dedicated custom store Of note, HBase 2.3.0 changes the in-Master Procedure Store implementation. It was a dedicated custom store
(see <<master.wal>>) to instead use a standard HBase Region (link:https://issues.apache.org/jira/browse/HBASE-23326). (see <<master.wal>>) to instead use a standard HBase Region (https://issues.apache.org/jira/browse/HBASE-23326[HBASE-23326]).
The migration from the old to new format is automatic run by the new 2.3.0 Master on startup. The old _MasterProcWALs_ The migration from the old to new format is automatic run by the new 2.3.0 Master on startup. The old _MasterProcWALs_
dir which hosted the old custom implementation files in _${hbase.rootdir}_ is deleted on successful dir which hosted the old custom implementation files in _${hbase.rootdir}_ is deleted on successful
migration. A new _MasterProc_ sub-directory replaces it to host the Store files and WALs for the new migration. A new _MasterProc_ sub-directory replaces it to host the Store files and WALs for the new