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-13883) Fix Memstore Flush section in HBase book
Date Sat, 20 Feb 2016 03:50:18 GMT

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

Hudson commented on HBASE-13883:
--------------------------------

FAILURE: Integrated in HBase-Trunk_matrix #723 (See [https://builds.apache.org/job/HBase-Trunk_matrix/723/])
HBASE-13883 Clarify the MemStore Flush section in the RefGuide (mstanleyjones: rev fea0dd46dd84b330ecab7addf30276181f8ae7c6)
* src/main/asciidoc/_chapters/architecture.adoc


> 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
>    Affects Versions: 2.0.0
>            Reporter: Vladimir Rodionov
>            Assignee: Misty Stanley-Jones
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13883.patch
>
>
> {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