hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15131) Turn on multi-WAL by default
Date Tue, 06 Jun 2017 11:46:18 GMT

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

Anoop Sam John commented on HBASE-15131:

In a mail chain in user@ Yu Li says
By default it's 32 which means for
each RS the un-archived wal number shouldn't exceed 32. However, when
multiwal enabled, it allows 32 logs for each group, thus becoming 64 wals
allowed for a single RS.
The #WALs  having some limit so that the data size to replay on a recovery is not too much.
 So when we have multi WAL, we should take that in to account and should reduce the # WAL
files per group accordingly?  Say in 2 WALs, per group 16 max?

> Turn on multi-WAL by default
> ----------------------------
>                 Key: HBASE-15131
>                 URL: https://issues.apache.org/jira/browse/HBASE-15131
>             Project: HBase
>          Issue Type: New Feature
>          Components: wal
>            Reporter: Enis Soztutar
>             Fix For: 2.0.0
> Something to discuss for 2.0 or even 1.3 or 1.4. Should we turn on multi-WAL by default
now that it has seen some production use. 
> Most of the known issues has been fixed I believe for replication, metrics etc. See HBASE-14457.

> Using bounded provider with default 4 (assuming 12 disks). Should we also look at the
number of disks from datanode dirs and auto-configure? 

This message was sent by Atlassian JIRA

View raw message