Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 21 May 2015 17:00:22 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12754128.1415622344000.1004.1432227622183@Atlassian.JIRA>
In-Reply-To: <JIRA.12754128.1415622344000@Atlassian.JIRA>
References: <JIRA.12754128.1415622344000@Atlassian.JIRA>
 <JIRA.12754128.1415622344156@arcas>
Subject: [jira] [Commented] (HBASE-12451)
 IncreasingToUpperBoundRegionSplitPolicy may cause unnecessary region splits
 in rolling update of cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-12451:
-------------------------------

Yes, I meant [~Apache9]'s comment.

Ok.

bq. Maybe a cluster-level switch of region split is a simpler solution for this problem.

What would it do? It would enable your average check?

bq. What's your suggestion?

What was there was broke as you point out. I suggest that we wait until you deploy this patch as is -- it is a good improvement -- and see how it does in production. If good, lets commit this patch.

> IncreasingToUpperBoundRegionSplitPolicy may cause unnecessary region splits in rolling update of cluster
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-12451
>                 URL: https://issues.apache.org/jira/browse/HBASE-12451
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-12451-v1.diff, HBASE-12451-v2.diff
>
>
> Currently IncreasingToUpperBoundRegionSplitPolicy is the default region split policy. In this policy, split size is the number of regions that are on this server that all are of the same table, cubed, times 2x the region flush size.
> But when unloading regions of a regionserver in a cluster using region_mover.rb, the number of regions that are on this server that all are of the same table will decrease, and the split size will decrease too, which may cause the left region split in the regionsever. Region Splits also happens when loading regions of a regionserver in a cluster. 
> A improvment may set a minimum split size in IncreasingToUpperBoundRegionSplitPolicy
> Suggestions are welcomed. Thanks~


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)