[
https://issues.apache.org/jira/browse/HDFS-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024945#comment-15024945
]
Zhe Zhang commented on HDFS-9289:
---------------------------------
Thanks Sangjin. Yes the conflicts were mostly trivial. I was just not sure if I
did the right update to CHANGES.TXT. I just committed the change to branch-2.6.
> Make DataStreamer#block thread safe and verify genStamp in commitBlock
> ----------------------------------------------------------------------
>
> Key: HDFS-9289
> URL: https://issues.apache.org/jira/browse/HDFS-9289
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Chang Li
> Assignee: Chang Li
> Priority: Critical
> Fix For: 3.0.0, 2.7.3, 2.6.3
>
> Attachments: HDFS-9289-branch-2.6.patch, HDFS-9289.1.patch,
> HDFS-9289.2.patch, HDFS-9289.3.patch, HDFS-9289.4.patch, HDFS-9289.5.patch,
> HDFS-9289.6.patch, HDFS-9289.7.patch, HDFS-9289.branch-2.7.patch,
> HDFS-9289.branch-2.patch
>
>
> we have seen a case of corrupt block which is caused by file complete after a
> pipelineUpdate, but the file complete with the old block genStamp. This
> caused the replicas of two datanodes in updated pipeline to be viewed as
> corrupte. Propose to check genstamp when commit block
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
