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 2017/02/01 22:00:53 UTC

[jira] [Updated] (HBASE-16755) Honor flush policy under global memstore pressure

     [ https://issues.apache.org/jira/browse/HBASE-16755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashu Pachauri updated HBASE-16755:
----------------------------------
    Fix Version/s: 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)