stack commented on HBASE-19997:

Ok. Can get a bit further. Can verify hbase;meta location on an hbase1 server. 
Now I fail because hbase:meta does not have new 'table' column family. Need to 
figure how to 'move' hbase:meta (can't disable the table to alter) and while 
moving, add new column family. Will be back.

> [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.0.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

Reply via email to