[
https://issues.apache.org/jira/browse/HBASE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707502#action_12707502
]
Andrew Purtell commented on HBASE-1302:
---------------------------------------
Failover activity can happen if the cluster is restarted relatively quickly. I
use a HBase ZK session timeout of 30000 (30 seconds). If I do stop-hbase.sh,
wait for the master to exit, then do a start-hbase.sh within a few seconds, I
see
2009-05-8 19:55;36,906 INFO org.apache.hadoop.hbase.master.HMaster: This is a
failover, ZK inspection begins...
2009-05-8 19:55;36,940 INFO org.apache.hadoop.ipc.HBaseClass: Retrying connect
to server: /172.20.3.229:60020. Already tried 0 time(s).
Then nothing.
> 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
>
>
> 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.
