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] [Commented] (HBASE-15131) Turn on multi-WAL by default
Date Wed, 07 Jun 2017 08:33:18 GMT

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

Yu Li commented on HBASE-15131:

Actually our current max log limitation logic is incorrect with multiwal. The calculation
is {{(globalMemstoreSize * 2) / logRollSize}} but at WAL level inside {{AbstractFSWAL}}, while
with multiwal this should be a global limit. We should also make it work with grouping strategy
which has unfixed group number such as IdentityGroupingStrategy. It's not a straight-forward
change so let me open another JIRA to address it.

In production, we're using BoundedGroupingStrategy and manually set the max log number for
each group, so no issue occurs.

> 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