[
https://issues.apache.org/jira/browse/HBASE-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485771#comment-14485771
]
Jonathan Hsieh commented on HBASE-13412:
----------------------------------------
I think it is a test problem
Based on :
{code}
Mockito.doReturn((long)(maxSplitSize * 1.025 + 1)).when(mockStore).getSize();
{code}
{code}
double jitter = conf.getDouble("hbase.hregion.max.filesize.jitter", 0.25D);
this.desiredMaxFileSize += (long)(desiredMaxFileSize * (RANDOM.nextFloat() -
0.5D) * jitter);
{code}
I think 1.025 should be 1.25.
> 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
>
> Attachments: HBASE-13412-v1.patch, HBASE-13412-v2.patch,
> HBASE-13412-v3.patch, HBASE-13412.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)
