[
https://issues.apache.org/jira/browse/HADOOP-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664378#action_12664378
]
Raghu Angadi commented on HADOOP-5027:
--------------------------------------
> The fix is described in the description and Dhruba's comment.
all right.
>> Btw, the patch just ignores such a block with a warning..., should it also
>> delete such a block?
>This case should not happen. If it happens, it indicates that there are bugs
>somewhere. Without knowing what is going on, it is better not delete the block.
adding something like "this is unexpected" to the message might make admins and
users report it back, if they notice it.
> Block report processing should compare gneration stamp
> ------------------------------------------------------
>
> Key: HADOOP-5027
> URL: https://issues.apache.org/jira/browse/HADOOP-5027
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: Tsz Wo (Nicholas), SZE
> Fix For: 0.19.1
>
> Attachments: 5027_20090114.patch
>
>
> If a reported block has a different generation stamp then the one stored in
> the NameNode, the reported block will be considered as invalid. This is
> incorrect since blocks with larger generation stamp are valid.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
