[
https://issues.apache.org/jira/browse/HBASE-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246385#comment-14246385
]
stack commented on HBASE-10201:
-------------------------------
I'm +1 on this going into master branch. I am +1 on this going into branch-1
but with it disabled by default as an experimental feature; users would have to
enable the FlushLargeStoresPolicy explicitly (You ok w/ that [~enis])?
Any chance of more +1s? [~jeffreyz]? Any other reviews out there? This is an
old issue, nicely addressed, that can make a nice dent in our i/o profile when
more than one column family but it would be good to get more eyes on it given
its messing with sequenceids. Thanks.
> Port 'Make flush decisions per column family' to trunk
> ------------------------------------------------------
>
> Key: HBASE-10201
> URL: https://issues.apache.org/jira/browse/HBASE-10201
> Project: HBase
> Issue Type: Improvement
> Components: wal
> Reporter: Ted Yu
> Assignee: zhangduo
> Fix For: 1.0.0, 2.0.0
>
> Attachments: 3149-trunk-v1.txt, HBASE-10201-0.98.patch,
> HBASE-10201-0.98_1.patch, HBASE-10201-0.98_2.patch, HBASE-10201-0.99.patch,
> HBASE-10201.patch, HBASE-10201_1.patch, HBASE-10201_10.patch,
> HBASE-10201_11.patch, HBASE-10201_12.patch, HBASE-10201_13.patch,
> HBASE-10201_13.patch, HBASE-10201_14.patch, HBASE-10201_15.patch,
> HBASE-10201_16.patch, HBASE-10201_17.patch, HBASE-10201_18.patch,
> HBASE-10201_19.patch, HBASE-10201_2.patch, HBASE-10201_3.patch,
> HBASE-10201_4.patch, HBASE-10201_5.patch, HBASE-10201_6.patch,
> HBASE-10201_7.patch, HBASE-10201_8.patch, HBASE-10201_9.patch,
> compactions.png, count.png, io.png, memstore.png
>
>
> Currently 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 was sent by Atlassian JIRA
(v6.3.4#6332)
