hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-3241) check to see if we exceeded hbase.regionserver.maxlogs limit is incorrect
Date Thu, 18 Nov 2010 00:57:14 GMT

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

Jean-Daniel Cryans resolved HBASE-3241.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.92.0
     Hadoop Flags: [Reviewed]

Committed to trunk and 0.90, thanks Kannan!

> 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, 0.92.0
>
>         Attachments: HBASE-3239-and-3241.txt
>
>
> 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.


Mime
View raw message