You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "xufeng (Commented) (JIRA)" <ji...@apache.org> on 2012/04/01 08:38:56 UTC
[jira] [Commented] (HBASE-5677) The master never does balance
because duplicate openhandled the one region
[ https://issues.apache.org/jira/browse/HBASE-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243668#comment-13243668 ]
xufeng commented on HBASE-5677:
-------------------------------
We can reproduce this issue by following steps with 0.90:
step1:start a cluster and create a table that has many regions.
step2:disable table created in step1 by shell.
step3:kill the active master.
step3:the backup master will become active one,when the master checkin regionservers. enable the table by shell.
result:the duplicate problem issue happened.
I think the master should not provide service when it did not complete the initialization.
We can add a method in HMasterInterface
like:
{noformat}
public boolean isMasterAvailable();
//the master is running and it can provide service
public boolean isMasterAvailable() {
return !isStopped() && isActiveMaster() && isInitialized();
}
{noformat}
When the client getMaster,we can check it.
pls give me the suggestions,thanks.
> The master never does balance because duplicate openhandled the one region
> --------------------------------------------------------------------------
>
> Key: HBASE-5677
> URL: https://issues.apache.org/jira/browse/HBASE-5677
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.6
> Environment: 0.90
> Reporter: xufeng
> Assignee: xufeng
>
> If region be assigned When the master is doing initialization(before do processFailover),the region will be duplicate openhandled.
> because the unassigned node in zookeeper will be handled again in AssignmentManager#processFailover()
> it cause the region in RIT,thus the master never does balance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira