hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDFS-9289) Make DataStreamer#block thread safe and verify genStamp in commitBlock
Date Mon, 02 Nov 2015 15:49:28 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985415#comment-14985415
] 

Daryn Sharp edited comment on HDFS-9289 at 11/2/15 3:49 PM:
------------------------------------------------------------

I'd rather see the InvalidGenStampException instead of a generic IOE.  Else it's hard for
client code to intelligently deal with exceptions and for tests to verify that the correct/expected
IOE was thrown.


was (Author: daryn):
I'd rather see the InvalidGenStampException instead of a generic IOE.  Else it's hard for
client code to intelligently deal with exceptions and for tests to verify that the correct/expected
IOE.

> 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
>
>
> 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)

Mime
View raw message