hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3320) Compaction parameter minCompactSize should be configurable
Date Wed, 08 Dec 2010 23:32:01 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969559#action_12969559
] 

stack commented on HBASE-3320:
------------------------------

+1 then

> Compaction parameter minCompactSize should be configurable
> ----------------------------------------------------------
>
>                 Key: HBASE-3320
>                 URL: https://issues.apache.org/jira/browse/HBASE-3320
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.0, 0.92.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.90.0, 0.92.0
>
>         Attachments: HBASE-3320-v1.patch, HBASE-3320-v2.patch
>
>
> In the new compaction algorithm, there is a minCompactSize parameter which is used to
include files in selection if they are under this size.
> Currently this is:
> {noformat}
>     this.minCompactSize = this.region.memstoreFlushSize * 3 / 2; // +50% pad
> {noformat}
> In a cluster, we had high setting of flush size but were doing frequent small flushes
because of HLog eviction.  This led to pathological cases in compaction file selection that
this algorithm is trying to avoid in the first place.
> Should make this configurable but the existing value should be fine for default in most
applications.

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


Mime
View raw message