[
https://issues.apache.org/jira/browse/HDFS-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938116#comment-14938116
]
Hudson commented on HDFS-8602:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #439 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/439/])
HDFS-8602. Erasure Coding: Client can't read(decode) the EC files which (jing9:
rev 8c423a8163bf7e27422e101f3d4768c3ca1a6b88)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestReadStripedFileWithDecoding.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSStripedInputStream.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES-HDFS-EC-7285.txt
> 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
>
> Attachments: HDFS-8602-HDFS-7285.01.patch, HDFS-8602.000.patch
>
>
> 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)
