[
https://issues.apache.org/jira/browse/HBASE-14651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-14651:
--------------------------
Attachment: bytes.png
files.png
I applied the patch [~vrodionov] and it does not seem to make any difference.
I have a cluster of 5 nodes with one RS on it. I load it using a YCSB
all-writes workload. I start with an empty table for both tests. I use 25
clients.
The count of files compacted and the number of bytes charts have the same shape
(its uncanny).
I checked that the patch was indeed applied.
> Default minimum compaction size is too high
> -------------------------------------------
>
> Key: HBASE-14651
> URL: https://issues.apache.org/jira/browse/HBASE-14651
> Project: HBase
> Issue Type: New Feature
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Attachments: HBASE-14651-v1.patch, HBASE-14651-v2.patch, bytes.png,
> files.png
>
>
> *hbase.hstore.compaction.min.size* defines minimum selection size which is
> always eligible for minor compaction (no compaction ratio check is performed
> on such file selections). Default size is equals to memstore flush size
> (128MB). First of all, even this value is too high for some (many)
> deployments, especially for write intensive, because of a small sizes of a
> memstore flushes, and if user increases memstore flush size (they usually set
> it to at least 256MB), they have no idea how will it impact the overall
> compaction process efficiency. With 256MB of minimum size to compact,
> compactor most of the time skips necessary file ratio checks and this will
> result in increased read/write IO during compactions, because of the
> unbalanced selections where relatively large files can be mixed with a newly
> created small store files. I think we should set this default minimum to
> 64MB and not to link it to memstore flush size at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
