[ https://issues.apache.org/jira/browse/HBASE-19172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-19172. --------------------------- Resolution: Duplicate HBASE-13032 did a form of this years ago. HBASE-13032 was refactored in HBASE-16060 which adds a unit test to prove this works. It also includes notes on how we verified this working on a cluster deploy. Resolving as duplicate. > [rolling upgrade] Migrate region state from zk to hbase:meta > ------------------------------------------------------------ > > Key: HBASE-19172 > URL: https://issues.apache.org/jira/browse/HBASE-19172 > Project: HBase > Issue Type: Sub-task > Components: migration > Reporter: stack > Priority: Major > Fix For: 2.0.0-beta-2 > > > HBASE-19165 is about starting a branch-2 over branch-1 dataset. The Master > when it comes up, goes to read the 'state' of the region from hbase:meta > because this is how region state is kept now by AMv2 only, there is no state > in hbase:meta on a fresh start. In hbase1, region state was kept in master > memory persisted to zk (rather than hbase:meta) while the region was in > transition. > We need to add to master a self-migration facility. If a region has no state > in hbase:meta, then look in zk to see if it RIT. If nothing in RIT, ask the > pertinent regionserver if it has the region. -- This message was sent by Atlassian JIRA (v7.6.3#76005)