[
https://issues.apache.org/jira/browse/HBASE-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924705#action_12924705
]
Jean-Daniel Cryans commented on HBASE-3149:
-------------------------------------------
I have been thinking about this one for some time... I think it makes sense in
loads of ways since a common problem of multi-CF is that during the initial
import the user ends up with thousands of small store files because some family
grows faster and triggered the flushes, which in turn generates incredible
compaction churn. On the other hand, it means that we almost consider a family
as a region e.g. one region with 3 CF can have up to 3x64MB in the memstores.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
