Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 20 Oct 2016 22:26:59 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13014022.1476990413000.45807.1477002419371@Atlassian.JIRA>
In-Reply-To: <JIRA.13014022.1476990413000@Atlassian.JIRA>
References: <JIRA.13014022.1476990413000@Atlassian.JIRA> <JIRA.13014022.1476990413449@arcas>
Subject: [jira] [Commented] (HBASE-16894) Create more than 1 split per
 region, generalize HBASE-12590
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 20 Oct 2016 22:27:01 -0000


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

Enis Soztutar commented on HBASE-16894:
---------------------------------------

bq. or should we pass a custom split list?
I think the users will generally not know these splits points. It should be hbase which keeps track of region boundaries and internally split points within the regions. As a user, the API should be like create a split for every 5GB, or there should be a total of X map tasks. 

> Create more than 1 split per region, generalize HBASE-12590
> -----------------------------------------------------------
>
>                 Key: HBASE-16894
>                 URL: https://issues.apache.org/jira/browse/HBASE-16894
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>
> A common request from users is to be able to better control how many map tasks are created per region. Right now, it is always 1 region = 1 input split = 1 map task. Same goes for Spark since it uses the TIF. With region sizes as large as 50 GBs, it is desirable to be able to create more than 1 split per region.
> HBASE-12590 adds a config property for MR jobs to be able to handle skew in region sizes. The algorithm is roughly: 
> {code}
> If (region size >= average size*ratio) : cut the region into two MR input splits
> If (average size <= region size < average size*ratio) : one region as one MR input split
> If (sum of several continuous regions size < average size * ratio): combine these regions into one MR input split.
> {code}
> Although we can set data skew ratio to be 0.5 or something to abuse HBASE-12590 into creating more than 1 split task per region, it is not ideal. But there is no way to create more with the patch as it is. For example we cannot create more than 2 tasks per region. 
> If we want to fix this properly, we should extend the approach in HBASE-12590, and make it so that the client can specify the desired num of mappers, or desired split size, and the TIF generates the splits based on the current region sizes very similar to the algorithm in HBASE-12590, but a more generic way. This also would eliminate the hand tuning of data skew ratio.
> We also can think about the guidepost approach that Phoenix has in the stats table which is used for exactly this purpose. Right now, the region can be split into powers of two assuming uniform distribution within the region. 


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