hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1302) When a new master comes up, regionservers should continue with their region assignments from the last master
Date Thu, 21 May 2009 23:59:45 GMT

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

stack commented on HBASE-1302:
------------------------------

+1 on this patch.

I spent some testing killing master bringing it back up again after a little while and all
continued without hiccup.  Commit!

Only issue I ran into was when I tried to start master on another machine.  Then things got
a little odd.  Had to change the master address -- as fellas have already speculated -- but
then I was getting this:

{code}
2009-05-21 23:58:28,669 [main] WARN org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Failed
to create /hbase:
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss
for /hbase
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:90)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:42)
        at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:518)
        at org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper.ensureExists(ZooKeeperWrapper.java:293)
        at org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper.ensureParentExists(ZooKeeperWrapper.java:314)
        at org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper.writeMasterAddress(ZooKeeperWrapper.java:402)
        at org.apache.hadoop.hbase.master.HMaster.writeAddressToZooKeeper(HMaster.java:259)
        at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:249)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:1093)
        at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1130)
{code}

Which seems wrong.  Why does it not just to assume what is under /hbase?

> 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.


Mime
View raw message