[
https://issues.apache.org/jira/browse/HBASE-20589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20589:
------------------------------
Fix Version/s: 2.1.0
3.0.0-alpha-1
> Don't need to assign meta to a new RS when standby master become active
> -----------------------------------------------------------------------
>
> Key: HBASE-20589
> URL: https://issues.apache.org/jira/browse/HBASE-20589
> Project: HBase
> Issue Type: Bug
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.1.0, 2.0.1
>
> Attachments: HBASE-20589.branch-2.0.patch,
> HBASE-20589.master.001.patch, HBASE-20589.master.002.patch,
> HBASE-20589.master.003.patch, HBASE-20589.master.003.patch,
> HBASE-20589.master.004.patch, HBASE-20589.master.005.patch,
> HBASE-20589.master.006.patch, HBASE-20589.master.007.patch,
> HBASE-20589.master.008.patch, HBASE-20589.master.008.patch,
> HBASE-20589.master.009.patch
>
>
> I found this problem when I write ut for HBASE-20569. Now the master
> finishActiveMasterInitialization introduce a new
> RecoverMetaProcedure(HBASE-18261) and it has a sub procedure AssignProcedure.
> AssignProcedure will skip assign a region when regions state is OPEN and
> server is online. But for the new regiog state node is created with state
> OFFLINE. So it will assign the meta to a new RS. And kill the old RS when old
> RS report to master. This will make the master initialization cost a long
> time. I will attatch a ut to show this. FYI [~stack]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
