[ 
https://issues.apache.org/jira/browse/HDFS-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chang Li updated HDFS-9289:
---------------------------
    Description: 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  (was: 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)

> check genStamp when complete file
> ---------------------------------
>
>                 Key: HDFS-9289
>                 URL: https://issues.apache.org/jira/browse/HDFS-9289
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>
> 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)

Reply via email to