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 Mon, 25 May 2009 18:30:45 GMT

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

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

Yes, I did as you speculated J-D.  I changed hbase-site.xml only.  And yes, I agree, we need
to fix it but it belongs elsewhere.

I took a quick look at patch and looks good.  I'd say go ahead and 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, 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.


Mime
View raw message