[
https://issues.apache.org/jira/browse/HBASE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans updated HBASE-1302:
--------------------------------------
Attachment: hbase-1302-v3.patch
Patch that fixes the NodeCreated/NodeDeleted confusion. Now I see:
{code}
2009-05-22 15:47:32,344 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Got ZooKeeper event, state:
SyncConnected, type: NodeCreated, path: /hbase/master
2009-05-22 15:47:32,345 DEBUG
org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Read ZNode /hbase/master
got 192.168.1.81:62000
2009-05-22 15:47:32,345 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Telling master at
192.168.1.81:62000 that we are up
....
....
2009-05-22 15:49:12,250 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Got ZooKeeper event, state:
SyncConnected, type: NodeDeleted, path: /hbase/master
2009-05-22 15:49:12,252 DEBUG
org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Set watcher on master
address ZNode /hbase/master
2009-05-22 15:49:12,285 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Got ZooKeeper event, state:
SyncConnected, type: NodeCreated, path: /hbase/master
2009-05-22 15:49:12,286 DEBUG
org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Read ZNode /hbase/master
got 192.168.1.83:62000
2009-05-22 15:49:12,286 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Telling master at
192.168.1.83:62000 that we are up
{code}
> 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,
> hbase-1302-v3.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.
