You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2017/03/10 01:46:38 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 ]
Gary Helmling updated HBASE-15429:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed the branch-1 patch to branch-1 and branch-1.3.
[~mantonov] I pulled this in to 1.3 since it's completely self contained and not used unless enabled. If you see an issue, let me know and I can revert.
> 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.4.0, 1.3.1
>
> Attachments: HBASE-15429.branch-1.patch, HBASE-15429.patch, HBASE-15429-V1.patch, HBASE-15429-V2.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.15#6346)