hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Rodionov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13883) Fix Memstore Flush section in HBase book
Date Wed, 10 Jun 2015 03:07:00 GMT

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

Vladimir Rodionov updated HBASE-13883:
--------------------------------------
    Description: 
{quote}
65.7.2. MemStore Flush

A MemStore flush can be triggered under any of the conditions listed below. The minimum flush
unit is per region, not at individual MemStore level.

 // SKIPPED

    3. When the number of WAL per region server reaches the value specified in hbase.regionserver.max.logs,
MemStores from various regions will be flushed out to disk to reduce WAL count. The flush
order is based on time. Regions with the oldest MemStores are flushed first until WAL count
drops below hbase.regionserver.max.logs.


{quote}

Section 3. requires clarification (reference to HBase version which supports this). Is it
MultiWAL feature in 1.0? 

  was:
{quote}
65.7.2. MemStore Flush

A MemStore flush can be triggered under any of the conditions listed below. The minimum flush
unit is per region, not at individual MemStore level.

  1.  When a MemStore reaches the size specified by hbase.hregion.memstore.flush.size, all
MemStores that belong to its region will be flushed out to disk.

    2. When the overall MemStore usage reaches the value specified by hbase.regionserver.global.memstore.upperLimit,
MemStores from various regions will be flushed out to disk to reduce overall MemStore usage
in a RegionServer. The flush order is based on the descending order of a region’s MemStore
usage. Regions will have their MemStores flushed until the overall MemStore usage drops to
or slightly below hbase.regionserver.global.memstore.lowerLimit.

    3. When the number of WAL per region server reaches the value specified in hbase.regionserver.max.logs,
MemStores from various regions will be flushed out to disk to reduce WAL count. The flush
order is based on time. Regions with the oldest MemStores are flushed first until WAL count
drops below hbase.regionserver.max.logs.


{quote}


> Fix Memstore Flush section in HBase book
> ----------------------------------------
>
>                 Key: HBASE-13883
>                 URL: https://issues.apache.org/jira/browse/HBASE-13883
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Vladimir Rodionov
>
> {quote}
> 65.7.2. MemStore Flush
> A MemStore flush can be triggered under any of the conditions listed below. The minimum
flush unit is per region, not at individual MemStore level.
>  // SKIPPED
>     3. When the number of WAL per region server reaches the value specified in hbase.regionserver.max.logs,
MemStores from various regions will be flushed out to disk to reduce WAL count. The flush
order is based on time. Regions with the oldest MemStores are flushed first until WAL count
drops below hbase.regionserver.max.logs.
> {quote}
> Section 3. requires clarification (reference to HBase version which supports this). Is
it MultiWAL feature in 1.0? 



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

Mime
View raw message