[
https://issues.apache.org/jira/browse/HBASE-16755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933867#comment-15933867
]
Gary Helmling commented on HBASE-16755:
---------------------------------------
[~enis], [~Apache9] -- how about the following approach:
* branch-1.3: commit the current patch. All of our existing FlushPolicy
implementations will flush something, but this won't enforce that something has
been flushed by any possible FlushPolicy implementation.
* branch-1 & master: in addition, make one of the changes Ashu described to
allow the flusher to enforce that something has always flushed, regardless of
the FlushPolicy implementation.
Does this seem reasonable, or are there concerns about the current patch going
in to 1.3.1?
> Honor flush policy under global memstore pressure
> -------------------------------------------------
>
> Key: HBASE-16755
> URL: https://issues.apache.org/jira/browse/HBASE-16755
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Ashu Pachauri
> Assignee: Ashu Pachauri
> Fix For: 1.3.1
>
> Attachments: HBASE-16755.v0.patch
>
>
> When global memstore reaches the low water mark, we pick the best flushable
> region and flush all column families for it. This is a suboptimal approach in
> the sense that it leads to an unnecessarily high file creation rate and IO
> amplification due to compactions. We should still try to honor the underlying
> FlushPolicy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
