[
https://issues.apache.org/jira/browse/HBASE-21075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586597#comment-16586597
]
Duo Zhang commented on HBASE-21075:
-----------------------------------
I think a possible way is that, we can introduce a config, if enabled, we will
wait until it is safe to do rolling upgrading, and then we just call
System.exit to shutdown the HMaster, so operators will know that it is OK to
deploy HMaster with the new code then.
The instructions will be:
1. Shutdown both active and standby masters.
2. Enable the rolling upgrading flag, and start only one master, still with the
old code.
3. Wait until the master quit, and confirm that there is a 'READY TO ROLLING
UPGRADE' message in the master log.
4. Start new masters with the new code.
WDYT sir? [~stack].
Thanks.
> Confirm that we can rolling upgrade from 2.0.x and 2.1.x to 2.2.x after
> HBASE-20881
> -----------------------------------------------------------------------------------
>
> Key: HBASE-21075
> URL: https://issues.apache.org/jira/browse/HBASE-21075
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0, 2.2.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
