hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16755) Honor flush policy under global memstore pressure
Date Wed, 01 Mar 2017 19:39:45 GMT

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

Gary Helmling commented on HBASE-16755:
---------------------------------------

[~Apache9], yes, currently with either FlushAllLargeStoresPolicy or FlushNonSloppyStoresFirstPolicy,
we still will fall back to all stores in the case that none of the stores meets the flush
threshold.  So we will still ensure that something is always flushed.

Thanks for taking a look, I'll go ahead and commit.

> 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)

Mime
View raw message