[
https://issues.apache.org/jira/browse/HBASE-21075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657226#comment-16657226
]
stack commented on HBASE-21075:
-------------------------------
I tried this. Seems to work:
...
2018-10-19 11:06:09,371 INFO [ProcExecTimeout] procedure2.ProcedureExecutor:
UPGRADE OK: All existed procedures have been finished, quit...
2018-10-19 11:06:09,373 INFO [Thread-4] regionserver.ShutdownHook: Shutdown
hook starting; hbase.shutdown.hook=true;
fsShutdownHook=org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@263558c9
2018-10-19 11:06:09,373 INFO [Thread-4] regionserver.HRegionServer: *****
STOPPING region server 'localhost,16020,1539972363652' *****
...
I suppose we could start a backup master that is the new code so it could take
over soon as the old one stops?
Hopefully we can figure a smoother transition by the time of 2.2 but lets
commit this in meantime. Thanks [~Apache9]
> 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, proc-v2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 2.1.1, 2.0.3
>
> Attachments: HBASE-21075.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
