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

HBASE-26636 Update the ref guide upgrading section to mention that the master issue when upgrading to 2.3 (#3989) 

Signed-off-by: GeorryHuang <huangzhuoyue@apache.org>
This commit is contained in:
Duo Zhang 2021-12-31 12:07:09 +08:00 committed by GitHub
parent b948ddbf21
commit fbc8046bc3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -357,6 +357,12 @@ Master itself. Otherwise, it is like any other with the Master process running f
archiving WALs when over-flushed, and so on. Its files are readable by standard Region and Store file
tooling for triage and analysis as long as they are pointed to the appropriate location in the filesystem.
Notice that, after the migration, you should make sure to not start an active master with old code,
as it can not recognize the new procedure store. So it is suggested to upgrade backup master(s) to
new 2.3 first, and then upgrade the active master. And unless explicitly mentioned, this is the
suggested way for all upgrading, i.e, upgrading backup master(s) first, then active master, and then
region servers.
[[upgrade2.2]]
=== Upgrade from 2.0 or 2.1 to 2.2+