[
https://issues.apache.org/jira/browse/HBASE-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333332#comment-17333332
]
Viraj Jasani commented on HBASE-20788:
--------------------------------------
Just wanted to circle back on this.
{quote}Usually it will be fine. As we will upgrade master at the end, so no one
will write to the new table state family. But if you have tables which have
REPLICATION_SCOPE set to 1, then for 2.1.0 there will be problem. In 2.1.0,
when opening a region with REPLICATION_SCOPE set to 1, we will write a barrier
in the new replication barrier family, for serial replication.
{quote}
[~zhangduo] [~zghao] Writing barrier in new replication barrier family (for
serial replication) is applicable even if we haven't enabled serial replication?
>From this discussion it looks like if we have RSGroup enabled and upgrade meta
>region in System RSGroup, even if RS with meta crashes, meta won't at least
>leave system RSGroup (we will have to upgrade RSGroup to 2.x first though).
> Write up a doc about how to rolling upgrade from 1.x to 2.x
> -----------------------------------------------------------
>
> Key: HBASE-20788
> URL: https://issues.apache.org/jira/browse/HBASE-20788
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0-alpha-1
>
> Attachments: HBASE-20788.master.001.patch,
> HBASE-20788.master.002.patch, HBASE-20788.patch
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
