[
https://issues.apache.org/jira/browse/HBASE-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212858#comment-13212858
]
Prakash Khemani commented on HBASE-5332:
----------------------------------------
The major compactions are jittered so that too many of them don't happen at the
same time. Rather than relying on random jitter, why can't the compaction
thread simply ensure that it doesn't schedule too many compactions at the same
time?
> Deterministic Compaction Jitter
> -------------------------------
>
> Key: HBASE-5332
> URL: https://issues.apache.org/jira/browse/HBASE-5332
> Project: HBase
> Issue Type: Improvement
> Reporter: Nicolas Spiegelberg
> Assignee: Nicolas Spiegelberg
> Priority: Minor
> Attachments: D1785.1.patch, D1785.2.patch, D1785.3.patch
>
>
> Currently, we add jitter to a compaction using "delay + jitter*(1 -
> 2*Math.random())". Since this is non-deterministic, we can get major
> compaction storms on server restart as half the Stores that were set to
> "delay + jitter" will now be set to "delay - jitter". We need a more
> deterministic way to jitter major compactions so this information can persist
> across server restarts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
