hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16755) Honor flush policy under global memstore pressure
Date Mon, 27 Mar 2017 21:20:41 GMT

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

Hudson commented on HBASE-16755:

FAILURE: Integrated in Jenkins build HBase-1.4 #681 (See [https://builds.apache.org/job/HBase-1.4/681/])
HBASE-16755 Honor flush policy under global memstore pressure (garyh: rev babb857940578b8f3da8a00cc1142e11cd2c72a0)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java

> 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

View raw message