hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Li (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-14906) Improvements on FlushLargeStoresPolicy
Date Wed, 02 Dec 2015 07:58:11 GMT
Yu Li created HBASE-14906:
-----------------------------

             Summary: Improvements on FlushLargeStoresPolicy
                 Key: HBASE-14906
                 URL: https://issues.apache.org/jira/browse/HBASE-14906
             Project: HBase
          Issue Type: Improvement
    Affects Versions: 2.0.0
            Reporter: Yu Li
            Assignee: Yu Li


When checking FlushLargeStoragePolicy, found below possible improving points:

1. Currently in selectStoresToFlush, we will do the selection no matter how many actual families,
which is not necessary for one single family

2. Default value for hbase.hregion.percolumnfamilyflush.size.lower.bound could not fit in
all cases, and requires user to know details of the implementation to properly set it. We
propose to use "hbase.hregion.memstore.flush.size/column_family_number" instead:
{noformat}
  <property>
    <name>hbase.hregion.percolumnfamilyflush.size.lower.bound</name>
    <value>16777216</value>
    <description>
    If FlushLargeStoresPolicy is used and there are multiple column families,
    then every time that we hit the total memstore limit, we find out all the
    column families whose memstores exceed a "lower bound" and only flush them
    while retaining the others in memory. The "lower bound" will be
    "hbase.hregion.memstore.flush.size / column_family_number" by default
    unless value of this property is larger than that. If none of the families
    have their memstore size more than lower bound, all the memstores will be
    flushed (just as usual).
    </description>
  </property>
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message