[
https://issues.apache.org/jira/browse/HBASE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712199#action_12712199
]
Jean-Daniel Cryans commented on HBASE-1302:
-------------------------------------------
Stack, if you used a hbase-handled ZK instance then your zoo.cfg got this line:
server.0=${hbase.master.hostname}:2888:3888
And when you changed hbase.master.hostname in hbase-site.xml it changed it
there too, so your new master tried to connect on itself. I'd say that stuff is
in the scope of 1357/1445. Waiting after your confirmation to commit.
> 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: Jean-Daniel Cryans
> Fix For: 0.20.0
>
> Attachments: hbase-1302-v1.patch, hbase-1302-v2.patch
>
>
> 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.
