hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-2282) Semi-harmless race between block reports and block invalidation
Date Wed, 19 Mar 2014 23:07:43 GMT

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

Tsz Wo Nicholas Sze resolved HDFS-2282.

    Resolution: Not A Problem

I believe this is "Not A Problem" anymore.  Please feel free to reopen it if it is not the

> Semi-harmless race between block reports and block invalidation
> ---------------------------------------------------------------
>                 Key: HDFS-2282
>                 URL: https://issues.apache.org/jira/browse/HDFS-2282
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions:, 0.24.0
>            Reporter: Todd Lipcon
>         Attachments: hdfs-2282-20.txt, hdfs-2282-20.txt
> In the 0.20.203 codebase, block reports are not synchronized in any way against mutations
to the actual file structure on disk. If a file is removed from a directory while the block
report is scanning that directory, it will be mistakenly reported as existing with a length
of 0, since File.length() on a non-existent file returns 0.
> This results in an error being logged on the DataNode when the NN sends it a second block
deletion request for the already-deleted block. I believe it to be harmless, but the error
message can concern users.
> This was fixed in the 0.20 code line in HDFS-2379.  This jira remains open to track the
port to 0.24.

This message was sent by Atlassian JIRA

View raw message