[
https://issues.apache.org/jira/browse/HADOOP-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663895#action_12663895
]
Tsz Wo (Nicholas), SZE commented on HADOOP-5027:
------------------------------------------------
> Doesn't NN already know what the latest genstamp should be?
When a block is being updated in lease recovery, some replicators might have a
gs larger then the one stored in the NameNode. If the update fails, the latest
gs may not be committed to the NameNode.
> 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
>
>
> 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.
