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] [Updated] (HBASE-16755) Honor flush policy under global memstore pressure
Date Mon, 27 Mar 2017 19:17:41 GMT

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

Gary Helmling updated HBASE-16755:
      Resolution: Fixed
    Release Note: Prior to this change, when the memstore low water mark is exceeded on a
regionserver, the regionserver will force flush all stores on the regions selected for flushing
until we drop below the low water mark.  With this change, the regionserver will continue
to force flush regions when above the memstore low water mark, but will only flush the stores
returned by the configured FlushPolicy.
          Status: Resolved  (was: Patch Available)

Committed to branch-1.3+.

[~ashu210890], please open a new issue to add safety checking in master & branch-1 that
the flush policy has actually flushed something, as discussed in the comments here.

> 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