[
https://issues.apache.org/jira/browse/HBASE-21075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595200#comment-16595200
]
stack commented on HBASE-21075:
-------------------------------
Trying to figure something that might be a little easier on the operator.
A clean shutdown should also work? Wait for quiescent amv2.. no assigning,
crashing, then do shutdown. Let me check if this makes for any
assign/unassigns. A tool could look at master wal proc and report if any
assign/unassigns outstanding.
Or, tool could look at master proc wals to see if outstanding assign/unassigns.
If none, kill masters (standby first). Re-run tool to be sure. Then start 2.2?
> 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)
