[
https://issues.apache.org/jira/browse/HBASE-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925090#action_12925090
]
Karthik Ranganathan commented on HBASE-3149:
--------------------------------------------
Yes, agreed that the memory implication is different.
Eventually, is it not better to enforce the memory limit by using a combination
of flush sizes and restricting the number of regions we create? Because ideally
we should allow different flush sizes for the different CF's as the KV sizes
could be way different...
Shall I just make this an option in the conf for now with the default the way
it is?
> 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.
