You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2020/05/26 10:53:00 UTC
[jira] [Commented] (HBASE-24416) RegionNormalizer spliting region
should not be limited by hbase.normalizer.min.region.count
[ https://issues.apache.org/jira/browse/HBASE-24416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116619#comment-17116619 ]
Guanghao Zhang commented on HBASE-24416:
----------------------------------------
[~Ddupg] Can you open a new PR to backport to branch-2.2? It had many conflicts when cherry-pick to branch-2.2. Thanks.
> RegionNormalizer spliting region should not be limited by hbase.normalizer.min.region.count
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-24416
> URL: https://issues.apache.org/jira/browse/HBASE-24416
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha-1
> Reporter: Sun Xin
> Assignee: Sun Xin
> Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> In method computePlanForTable of SimpleRegionNormalizer:
> we will skip spliting region if the number of regions in the table is less than hbase.normalizer.min.region.count, even if there is a huge region in the table.
> {code:java}
> ...
> if (tableRegions == null || tableRegions.size() < minRegionCount) {
> ...
> return null;
> }
> ...
> // get region split plan
> if (splitEnabled) {
> List<NormalizationPlan> splitPlans = getSplitNormalizationPlan(table);
> if (splitPlans != null) {
> plans.addAll(splitPlans);
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)