[
https://issues.apache.org/jira/browse/HBASE-15429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904325#comment-15904325
]
Hudson commented on HBASE-15429:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #6 (See
[https://builds.apache.org/job/HBase-1.3-IT/6/])
HBASE-15429 Add split policy for busy regions (garyh: rev
0db1e0f7a80da125d3819e5e6efd8b7af09ffe31)
* (edit) hbase-common/src/main/resources/hbase-default.xml
* (add)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/BusyRegionSplitPolicy.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionSplitPolicy.java
> 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)
