[
https://issues.apache.org/jira/browse/HBASE-20589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481463#comment-16481463
]
Guanghao Zhang commented on HBASE-20589:
----------------------------------------
{quote}bq." 1 regions were assigned to random hosts, since the old hosts for
these regions are no longer present in the cluster. ".
{quote}
The log shows the old host no longer present in the cluster. But the UT only
stop active master and do nothing for RS. So the host should still be present
in the cluster.
> 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
> Attachments: 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
>
>
> 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
(v7.6.3#76005)
