You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Ashu Pachauri (JIRA)" <ji...@apache.org> on 2016/10/12 23:58:22 UTC

[jira] [Commented] (HBASE-16755) Don't flush everything when under global memstore pressure

    [ https://issues.apache.org/jira/browse/HBASE-16755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570289#comment-15570289 ] 

Ashu Pachauri commented on HBASE-16755:
---------------------------------------

Picking this up.

> Don't flush everything when 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
>
> 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.4#6332)