You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2009/10/28 08:45:59 UTC
[jira] Commented: (HADOOP-4735) NameNode reporting 0 size for
originally non-empty files
[ https://issues.apache.org/jira/browse/HADOOP-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770817#action_12770817 ]
dhruba borthakur commented on HADOOP-4735:
------------------------------------------
hi christian, we are starting to see similar problems in our old 0.17 cluster. Files that were written a coupel of days earlier tunr out to be zero size files. The replicas of the blocks of these files on the datanode actually have valid data. Stopping one of the datanodes causes the block to get replciaed, and updates the length of the file correctly on the namenode. Do you remember what fixes you migth have pulled in to avoid this problem? Thanks.
> NameNode reporting 0 size for originally non-empty files
> --------------------------------------------------------
>
> Key: HADOOP-4735
> URL: https://issues.apache.org/jira/browse/HADOOP-4735
> Project: Hadoop Common
> Issue Type: Bug
> 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.