[
https://issues.apache.org/jira/browse/HBASE-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-13412:
-----------------------------------
Fix Version/s: 0.98.13
Both the original commit and addendum picked back to 0.98 cleanly and the new
test passes repeatedly (ran it 10 times)
This change introduces a new configuration parameter and a behavioral change
for ConstantSizeRegionSplitPolicy and policies that inherit from it. The change
is desirable (it's the raison d'etre of this issue) but to alleviate any
compatibility concerns I committed an addendum to 0.98 only that will not apply
jitter unless the new configuration parameter is explicitly set.
> Region split decisions should have jitter
> -----------------------------------------
>
> Key: HBASE-13412
> URL: https://issues.apache.org/jira/browse/HBASE-13412
> Project: HBase
> Issue Type: New Feature
> Components: regionserver
> Affects Versions: 1.0.0, 2.0.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 2.0.0, 1.1.0, 0.98.13
>
> Attachments: HBASE-13412-v1.patch, HBASE-13412-v2.patch,
> HBASE-13412-v3.patch, HBASE-13412.addendum.0.98.patch, HBASE-13412.patch,
> hbase-13412.addendum.patch
>
>
> Whenever a region splits it causes lots of IO (compactions are queued for a
> while). Because of this it's important to make sure that well distributed
> tables don't have all of their regions split at exactly the same time.
> This is basically the same as our compaction jitter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
