hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kannan Muthukkaruppan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3189) Stagger Major Compactions
Date Thu, 04 Nov 2010 04:35:47 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928122#action_12928122

Kannan Muthukkaruppan commented on HBASE-3189:

I think, usability wise, jitter (and it's default) should be specified as fraction (% value)
of the major compaction cycle time, instead of absolute terms (like 4 hours)/

Otherwise, you have a backward compat issue with this change for someone who is running a
major compaction say every three hours, but has forgotten to set the jitter parameter when
they upgrade to 0.90. And they'll be compacting anywhere from 3hrs +/- (2* 4 hours jitter
default). This approach will also ensure you don't return -ve values for "get next compaction

> Stagger Major Compactions
> -------------------------
>                 Key: HBASE-3189
>                 URL: https://issues.apache.org/jira/browse/HBASE-3189
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Nicolas Spiegelberg
>            Assignee: Nicolas Spiegelberg
>            Priority: Minor
>             Fix For: 0.90.0
>         Attachments: HBASE-3189.patch
> For pre-split regions, we can get into a case where the oldest HFile in a Store is pretty
large and will not encounter a compaction within the 24hr major compact window.  If that's
the case, we don't want multiple multi-GB major compactions being triggered at the same time.
 Add ability to stagger the major compaction expiration window.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message