[
https://issues.apache.org/jira/browse/HBASE-21075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586653#comment-16586653
]
stack commented on HBASE-21075:
-------------------------------
Don't we need this even if it is a stop/start upgrade, not just for a rolling
upgrade? We need to clear out the old-style Procedures for both cases?
Could we make setting the flag dynamic? A page where you set the config and the
Master then runs until it has cleared out the old stuff and then System.exits
(Yeah, I like your System.exit idea).
> 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)
