[jira] Commented: (HBASE-1302) When a new master comes up, regionservers should continue with their region assignments from the last master

["Jim Kellerman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694236#action_12694236 ] 

Jim Kellerman commented on HBASE-1302:
--------------------------------------

What I would expect to happen is in Master.run() before calling startServiceThreads, the master should query ZK for known region servers and populate serversToServerInfo.

In the case of a cluster that is already running, the master then needs to find out which server is serving the root region.

Then, before calling startServiceThreads, it should invoke the method that recovers dead region server logs (HBASE-698).
Making this issue a blocker for HBASE-698

> When a new master comes up, regionservers should continue with their region assignments from the last master
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1302
>                 URL: https://issues.apache.org/jira/browse/HBASE-1302
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.20.0
>            Reporter: Nitay Joffe
>            Assignee: Nitay Joffe
>             Fix For: 0.20.0
>
>
> After HBASE-1205, we can now handle a master going down and coming up somewhere else. When this happens, the new master will scan everything and reassign all the regions, which is not ideal. Instead of doing that, we should keep the region assignments from the last master. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.