[
https://issues.apache.org/jira/browse/HBASE-13883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157419#comment-15157419
]
Sean Busbey commented on HBASE-13883:
-------------------------------------
bq. As a follow on, Sean Busbey does enabling multiwal deserve bumping up the
hbase.regionserer.max.logs value?
Nah. The settings has been deprecated in preference for a calculated default.
{code}
boolean maxLogsDefined = conf.get("hbase.regionserver.maxlogs") != null;
if(maxLogsDefined){
LOG.warn("'hbase.regionserver.maxlogs' was deprecated.");
}
this.maxLogs = conf.getInt("hbase.regionserver.maxlogs",
Math.max(32, calculateMaxLogFiles(memstoreRatio, logrollsize)));
{code}
Also it's already done per WAL pipeline, so you get more when you enable
multiwal.
> 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)
