hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Kunz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4735) NameNode reporting 0 size for originally non-empty files
Date Wed, 26 Nov 2008 23:58:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651186#action_12651186
] 

Christian Kunz commented on HADOOP-4735:
----------------------------------------

They were created 11/16 (I found the corresponding log messages on the Namenode, no other
log messages referring to these blocks) and used as non-empty files by subsequent jobs (non-empty
otherwise they would have failed as mentioned in the description). They must have been become
empty within the last few days.

I checked one of the blocks on one of the datanodes after namenode restart. Still there and
still non-empty.

I will now move the empty files away into a different location (they will still be available
for examination) and re-create the original files from the non-empty blocks.

> NameNode reporting 0 size for originally non-empty files
> --------------------------------------------------------
>
>                 Key: HADOOP-4735
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4735
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.17.2
>            Reporter: Christian Kunz
>
> NameNode reports 0 size for a handful of files that were non-empty originally.
> The corresponding blocks on the DataNodes are non-empty.
> NameNode must have reported correct size at some time, because applications that would
have failed with 0 size files, executed successfully.

-- 
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