You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/24 00:50:39 UTC
[jira] [Resolved] (HDFS-591) Namenode should mark the replica as
corrupted if a DN has reported different length of a Complete block
[ https://issues.apache.org/jira/browse/HDFS-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved HDFS-591.
-----------------------------------
Resolution: Duplicate
> Namenode should mark the replica as corrupted if a DN has reported different length of a Complete block
> -------------------------------------------------------------------------------------------------------
>
> Key: HDFS-591
> URL: https://issues.apache.org/jira/browse/HDFS-591
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Konstantin Boudnik
>
> it has been found that NameNode is updating the length of a Complete block when its reported by a DataNode. As demonstrated by BlockReport.messWithBlocksLen() test ([see HDFS-551's patch|https://issues.apache.org/jira/secure/attachment/12418437/HDFS-551.patch]), when the length of blocks is changed and a block report is forced for the set of the blocks NameNode updates these lengths in memory, instead of marking such replicas as corrupted.
> It seems to be a wrong behavior.
--
This message was sent by Atlassian JIRA
(v6.2#6252)