hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guangxu Cheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17784) Check if the regions are deployed in the correct group, and move it to the correct group when starting master
Date Tue, 25 Apr 2017 02:37:04 GMT

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

Guangxu Cheng commented on HBASE-17784:
---------------------------------------

bq.Shouldn't we correct these misplaced regions when balancing?
Load balancer can correct these misplaced regions.
But there may be the following problems.
1. If the Load Balancer is not enabled, we need to manually trigger it.
2. By default, the load balancer is executed once for 5 minutes, regions are deployed in the
incorrect group in this period, which is inconsistent with the system. 
It may also affect the stability of other groups
3. The load balancer may trigger more region migration, and these regions may not need to
move.

It is a better choice to check and move regions to the correct group when starting master,
which also makes the system more robust. 

> Check if the regions are deployed in the correct group, and move it to the correct group
when starting master
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17784
>                 URL: https://issues.apache.org/jira/browse/HBASE-17784
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Guangxu Cheng
>            Assignee: Guangxu Cheng
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17784-v1.patch
>
>
> During move_servers_rsgroups/move_tables_rsgroups, if master crashes, it may lead to
some of the regions did not move to correct group.
> So when restart master, we should fix it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message