hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16765) New SteppingRegionSplitPolicy, avoid too aggressive spread of regions for small tables.
Date Wed, 02 Nov 2016 06:08:59 GMT

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

stack updated HBASE-16765:
--------------------------
        Priority: Critical  (was: Major)
    Hadoop Flags: Incompatible change

Marking as incompatible change (for 2.0) and marking critical so gets called out in 2.0.0
release notes.

> 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.4, 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.4#6332)

Mime
View raw message