[jira] [Commented] (HDFS-8602) Erasure Coding: Client can't read(decode) the EC files which have corrupt blocks.

["Walter Su (JIRA)" <ji...@apache.org>]

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

Walter Su commented on HDFS-8602:
---------------------------------

How does {{DFSInputStream}} handle this: {{fetchBlockByteRange}} will choose another DN when it got a IOException from current DN.
I think we should implement the similar logic in {{DFSStripedInputStream}}.

> Erasure Coding: Client can't read(decode) the EC files which have corrupt blocks.
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-8602
>                 URL: https://issues.apache.org/jira/browse/HDFS-8602
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Takanobu Asanuma
>            Assignee: Kai Sasaki
>             Fix For: HDFS-7285
>
>
> Before the DataNode(s) reporting bad block(s), when Client reads the EC file which has bad blocks, Client gets hung up. And there are no error messages.
> (When Client reads the replicated file which has bad blocks, the bad blocks are reconstructed at the same time, and Client can reads it.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)