You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2017/03/01 05:14:45 UTC

[jira] [Updated] (HBASE-16765) New SteppingRegionSplitPolicy, avoid too aggressive spread of regions for small tables.

     [ https://issues.apache.org/jira/browse/HBASE-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-16765:
--------------------------------
    Fix Version/s:     (was: 1.2.4)
                   1.2.5

> New SteppingRegionSplitPolicy, avoid too aggressive spread of regions for small tables.
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-16765
>                 URL: https://issues.apache.org/jira/browse/HBASE-16765
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Critical
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.5, 0.98.24, 1.1.8
>
>         Attachments: 16765-0.98.txt
>
>
> We just did some experiments on some larger clusters and found that while using IncreasingToUpperBoundRegionSplitPolicy generally works well and is very convenient, it does tend to produce too many regions.
> Since the logic is - by design - local, checking the number of regions of the table in question on the local server only, we end with more regions then necessary.



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