[
https://issues.apache.org/jira/browse/HBASE-16755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892875#comment-15892875
]
Enis Soztutar commented on HBASE-16755:
---------------------------------------
bq. This requires changing the LimitedPrivate Region api, and may not make
sense to do for a point release.
This seems like an improvement, and not a bug. And the risk is non-trivial as
per above. So, I would say it should not go to 1.3.1 anyway. It can be 1.4, and
2.0.
> 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)
