hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8481) Erasure coding: remove workarounds in client side stripped blocks recovering
Date Sat, 30 May 2015 00:43:17 GMT

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

Kai Zheng commented on HDFS-8481:
---------------------------------

bq. To address the GC issue we should also avoid filling 0 bytes. Maybe the codec can support
a special flag to mark an input slot as all-zero?
Good idea! It's easy to add such flag in {{ECChunk}} and we can use the following version
API:
{code}
public void decode(ECChunk[] inputs, int[] erasedIndexes, ECChunk[] outputs);
{code}
bq. how about we commit it first while we work on the various tasks discussed above to reuse
all input and output buffers?
I'm OK with this approach. 

> Erasure coding: remove workarounds in client side stripped blocks recovering
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-8481
>                 URL: https://issues.apache.org/jira/browse/HDFS-8481
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>         Attachments: HDFS-8481-HDFS-7285.00.patch, HDFS-8481-HDFS-7285.01.patch, HDFS-8481-HDFS-7285.02.patch,
HDFS-8481-HDFS-7285.03.patch, HDFS-8481-HDFS-7285.04.patch
>
>
> After HADOOP-11847 and related fixes, we should be able to properly calculate decoded
contents.



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

Mime
View raw message