Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <26770527.134751289958074657.JavaMail.jira@thor>
Date: Tue, 16 Nov 2010 20:41:14 -0500 (EST)
From: "Kannan Muthukkaruppan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Assigned: (HBASE-3241) check to see if we exceeded
 hbase.regionserver.maxlogs limit is incorrect
In-Reply-To: <11360653.130311289953154035.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kannan Muthukkaruppan reassigned HBASE-3241:
--------------------------------------------

    Assignee: Kannan Muthukkaruppan

> check to see if we exceeded hbase.regionserver.maxlogs limit is incorrect
> -------------------------------------------------------------------------
>
>                 Key: HBASE-3241
>                 URL: https://issues.apache.org/jira/browse/HBASE-3241
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Kannan Muthukkaruppan
>            Assignee: Kannan Muthukkaruppan
>
> In HLog.java:cleanOldLogs(), the number of logs left after archiving of old logs is computed as:
> {code}
>     int logCount = this.outputfiles.size() - logsToRemove;
> {code}
> However, the archival itself already removes the files that were archived from the "this.outputfiles" map. 
> So shouldn't the above logic simply be the following?
> {code}
>   int logCount = this.outputfiles.size();
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.