[ https://issues.apache.org/jira/browse/HDFS-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chang Li updated HDFS-9289:
---------------------------
Attachment: HDFS-9289.7.patch
Thanks [~daryn] and [~zhz] for review and comment!
I have talked to Daryn and he agrees to relegate the new exception work to a new jira.
the updated .7 address [~zhz]'s suggestion of consolidate two methods of {{addBlockToFile}}
and {{addStripedBlockToFile}} and rename {{TestCommitBlock}} class to {{TestCommitBlockWithInvalidGenStamp}}
> 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
> Reporter: Chang Li
> Assignee: Chang Li
> Priority: Critical
> Attachments: 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
>
>
> 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)