hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8813) Erasure Coding: Client no need to decode missing parity blocks
Date Wed, 30 Sep 2015 19:38:17 GMT

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

Hudson commented on HDFS-8813:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #465 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/465/])
HDFS-8813. Erasure Coding: Client no need to decode missing parity (jing9: rev c2c26e6ea7967f02c284918f68554334d4af8561)
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/util/StripedBlockUtil.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 no need to decode missing parity blocks
> --------------------------------------------------------------
>
>                 Key: HDFS-8813
>                 URL: https://issues.apache.org/jira/browse/HDFS-8813
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Walter Su
>            Assignee: Walter Su
>            Priority: Minor
>             Fix For: HDFS-7285
>
>         Attachments: HDFS-8813-HDFS-7285.01.patch
>
>
> Assume 6+3 schema.
> Assume data block #2 is missing, then InputStream tries to read parity block #6.
> Assume parity block #6 is missing too. And InputStream successfully reads parity block
#7.
> Then begin to decode.
> Currently InputStream will decode #2 and #6. But client(user) only need #2. The parity
block #6 will be disposed.
> The improvement is we only decode #2.



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

Mime
View raw message