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

Posted to issues@hbase.apache.org by "Ashu Pachauri (JIRA)" <ji...@apache.org> on 2016/06/02 00:46:59 UTC

[jira] [Updated] (HBASE-15429) Add a split policy for busy regions

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

Ashu Pachauri updated HBASE-15429:
----------------------------------
    Attachment: HBASE-15429-V1.patch

HBASE-15429-V1.patch:
Removed the properties from HTableDescriptor. Modified the defaults to be more aggressive and added a description for the BusyRegionSplitPolicy class.

> Add a split policy for busy regions
> -----------------------------------
>
>                 Key: HBASE-15429
>                 URL: https://issues.apache.org/jira/browse/HBASE-15429
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: HBASE-15429-V1.patch, HBASE-15429.patch
>
>
> Currently, all region split policies are based on size. However, in certain cases, it is a wise choice to make a split decision based on number of requests to the region and split busy regions.
> A crude metric is that if a region blocks writes often and throws RegionTooBusyExceoption, it's probably a good idea to split it.



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