[HBASE-19997] [rolling upgrade] 1.x => 2.x

• Type: Umbrella
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Release Note: Now we have a 'basically work' solution for rolling upgrade from 1.4.x to 2.x. Please see the "Rolling Upgrade from 1.x to 2.x" section in ref guide for more details.
• Assignee: Duo Zhang
• Reporter: Michael Stack
• Created: 14/Feb/18 04:20
• Updated: 23/Jun/22 19:17
• Resolved: 29/Jun/18 12:47

Description

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.

Issue Links

• relates to: HBASE-11059 ZK-less region assignment
• relates to: HBASE-19166 AsyncProtobufLogWriter persists ProtobufLogWriter as class name for backward compatibility
• relates to: HBASE-13147 Load actual META table descriptor, don't use statically defined one.
• relates to: HBASE-18494 [AMv2] Modify LoadBalancer to consider highest versioned Region Servers as favorites for system table regions
• relates to: HBASE-20746 Release 2.1.0
• links to: Auto-migration doc