[
https://issues.apache.org/jira/browse/HBASE-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212166#comment-13212166
]
stack commented on HBASE-3149:
------------------------------
@Nicolas I wonder about this... hbase.hstore.compaction.min.size. When we
compact, don't we have to take adjacent files as part of our ACID guarantees?
This would frustrate that? (I'll take a look... tomorrow). I'm wondering
because i want to figure how to make it so we favor reference files... so they
are always included in a compaction.
> Make flush decisions per column family
> --------------------------------------
>
> Key: HBASE-3149
> URL: https://issues.apache.org/jira/browse/HBASE-3149
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Karthik Ranganathan
> Assignee: Nicolas Spiegelberg
> Fix For: 0.92.1
>
>
> Today, the flush decision is made using the aggregate size of all column
> families. When large and small column families co-exist, this causes many
> small flushes of the smaller CF. We need to make per-CF flush decisions.
--
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
