[
https://issues.apache.org/jira/browse/HBASE-19997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520564#comment-16520564
]
stack commented on HBASE-19997:
-------------------------------
[~Xiaolin Ha] RegionServers first? We can't assign regions during this time,
right? Is that the NPE? Could we fix that in 2.0.x RS? Tell us more. Old 0.98
clients shouldn't work against 2.0 because they depend on a method that is no
longer supported, getClosestOrBefore. I thought you'd have to be 1.2 at least.
Would be great if a rolling upgrade worked.
> [rolling upgrade] 1.x => 2.x
> ----------------------------
>
> Key: HBASE-19997
> URL: https://issues.apache.org/jira/browse/HBASE-19997
> Project: HBase
> Issue Type: Umbrella
> Reporter: stack
> Priority: Blocker
> Fix For: 2.1.0
>
> Attachments: Screenshot from 2018-05-03 14-43-46.png
>
>
> An umbrella issue of issues needed so folks can do a rolling upgrade from
> hbase-1.x to hbase-2.x.
> (Recent) Notables:
> * hbase-1.x can't read hbase-2.x WALs -- hbase-1.x doesn't know the
> AsyncProtobufLogWriter class used writing the WAL -- see
> https://issues.apache.org/jira/browse/HBASE-19166?focusedCommentId=16362897&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16362897
> for exception.
> ** Might be ok... means WAL split fails on an hbase1 RS... must wait till an
> hbase-2.x RS picks up the WAL for it to be split.
> * hbase-1 can't open regions from tables created by hbase-2; it can't find
> the Table descriptor. See
> https://issues.apache.org/jira/browse/HBASE-19116?focusedCommentId=16363276&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16363276
> ** This might be ok if the tables we are doing rolling upgrade over were
> written with hbase-1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
