[
https://issues.apache.org/jira/browse/HBASE-19997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461913#comment-16461913
]
stack commented on HBASE-19997:
-------------------------------
Hello [~Xiaolin Ha] Thanks for taking a look at this one.
On the NPE, I hacked something. Don't remember what. It had to do w/ startup
sequence in Master. What is the exception on the regionserver side? That might
remind me.
Why you doing RS first and then Master? Does it work? I'd think you'd have to
do Master first no? Maybe you have a better idea?
Coming up from 0.98, you'd need to figure a solution for HBASE-20237. Old
clients will sometimes fail finding a region in hbase:meta. See comments on
that issue. Ask again if not clear.
> [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
>
>
> 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)
