[
https://issues.apache.org/jira/browse/HADOOP-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664351#action_12664351
]
shv edited comment on HADOOP-5027 at 1/15/09 5:29 PM:
----------------------------------------------------------------------
May be the problem is not with the block report, but rather with
{{nextGenerationStamp(Block)}}, which does not update generation stamp for the
block. The -client- _data-node_ should call name-node to obtain a new
generation stamp any way, I believe this what Raghu meant? So why do we not
changing the gen stamp of the block.
I also would like to see a unit test catching this bug.
was (Author: shv):
May be the problem is not with the block report, but rather with
{{nextGenerationStamp(Block)}}, which does not update generation stamp for the
block. The client should call name-node to obtain a new generation stamp any
way, I believe this what Raghu meant? So why do we not changing the gen stamp
of the block.
I also would like to see a unit test catching this bug.
> 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.
