You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Gray (JIRA)" <ji...@apache.org> on 2010/11/17 15:50:13 UTC
[jira] Updated: (HBASE-3241) check to see if we exceeded
hbase.regionserver.maxlogs limit is incorrect
[ https://issues.apache.org/jira/browse/HBASE-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Gray updated HBASE-3241:
---------------------------------
Priority: Blocker (was: Major)
Marking as blocker against 0.90. We should definitely get this and HBASE-3241 in.
> 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
> Affects Versions: 0.90.0
> Reporter: Kannan Muthukkaruppan
> Assignee: Kannan Muthukkaruppan
> Priority: Blocker
> Fix For: 0.90.0
>
>
> 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.