hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-4617) warning while purging logs with QJM enabled
Date Thu, 28 Mar 2013 04:45:17 GMT

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

Todd Lipcon resolved HDFS-4617.

    Resolution: Duplicate

ATM points out that I already found this bug 3 months ago... resolving as duplicate with HDFS-4298
> warning while purging logs with QJM enabled
> -------------------------------------------
>                 Key: HDFS-4617
>                 URL: https://issues.apache.org/jira/browse/HDFS-4617
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, namenode, qjm
>    Affects Versions: 2.0.3-alpha
>            Reporter: Todd Lipcon
> HDFS-2946 changed the way that edit log purging is calculated, such that it calls selectInputStreams()
with an arbitrary transaction ID calculated relative to the current one. The JournalNodes
will reject such a request if that transaction ID falls in the middle of a segment (which
it usually will). This means that selectInputStreams gets an exception, and the QJM journal
manager is not included in this calculation. Additionally, a warning will be logged.
> Purging itself still happens, because the detailed information on remote logs is not
necessary to calculate a retention interval, but the feature from HDFS-2946 may not work as

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message