Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 9 Dec 2015 18:55:11 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12920199.1449610935000.316231.1449687311048@Atlassian.JIRA>
In-Reply-To: <JIRA.12920199.1449610935000@Atlassian.JIRA>
References: <JIRA.12920199.1449610935000@Atlassian.JIRA>
 <JIRA.12920199.1449610935522@arcas>
Subject: [jira] [Commented] (HBASE-14951) Make hbase.regionserver.maxlogs
 obsolete
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Enis Soztutar commented on HBASE-14951:
---------------------------------------

+1. The checkstyle warning is this:  
{code}
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java	LeftCurlyCheck	0	1
{code}

I can fix it in commit. [~eclark], [~saint.ack@gmail.com] FYI. 


> Make hbase.regionserver.maxlogs obsolete
> ----------------------------------------
>
>                 Key: HBASE-14951
>                 URL: https://issues.apache.org/jira/browse/HBASE-14951
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>            Priority: Minor
>             Fix For: 2.0.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)