hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14951) Make hbase.regionserver.maxlogs obsolete
Date Tue, 22 Dec 2015 20:09:46 GMT

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

stack commented on HBASE-14951:
-------------------------------

bq. Yes, 2 is arbitrary.

Ok. Say so in release notes when explaining equation.

bq. ...artificial limit of hbase.regionserver.maxlogs

Its not artificial, though, right? We want to clean up WALs. If we have too many WALs, the
MTTR suffers.. takes longer because more to replay.

bq.  User has three options, either override default hbase.regionserver.maxlogs or override
default hbase.regionserver.logroll.period, or both to control runaway WALs. I will update
Release notes.

I'm concerned about defaults. Users will only consider this option after their cluster has
crashed and burned and won't start because thousands of WAL that need cleaning up preventing
cluster coming back promptly.

So with 2*, that means that if heap is 31G, then new default is 256 or is it 2* 256? Thanks
V.

> Make hbase.regionserver.maxlogs obsolete
> ----------------------------------------
>
>                 Key: HBASE-14951
>                 URL: https://issues.apache.org/jira/browse/HBASE-14951
>             Project: HBase
>          Issue Type: Improvement
>          Components: Performance, wal
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>            Priority: Minor
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: HBASE-14951-v1.patch, HBASE-14951-v2.patch
>
>
> There was a discussion in HBASE-14388 related to maximum number of log files. It was
an agreement that we should calculate this number in a code but still need to honor user's
setting. 
> Maximum number of log files now is calculated as following:
>  maxLogs = HEAP_SIZE * memstoreRatio * 2/ LogRollSize



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

Mime
View raw message