[
https://issues.apache.org/jira/browse/HDFS-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972046#comment-14972046
]
Jing Zhao commented on HDFS-9298:
---------------------------------
For GS smaller than the current one, there may be some race conditions between
writing recovery and block report. For example, we can have this scenario: the
GS recorded on NN gets bumped during the recovery, while a block report that
still contains the old GS gets delayed on the network thus is received
afterwards. Thus it may be better for NN not to make any decision while the
block is still UC.
> remove replica and not add replica with wrong genStamp
> ------------------------------------------------------
>
> Key: HDFS-9298
> URL: https://issues.apache.org/jira/browse/HDFS-9298
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: HDFS-9298.1.patch
>
>
> currently, in setGenerationStampAndVerifyReplicas, replica with wrong gen
> stamp is not really removed, only StorageLocation of that replica is removed.
> Moreover, we should check genStamp before addReplicaIfNotPresent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
