hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SammiChen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11268) Correctly reconstruct erasure coding file from FSImage
Date Thu, 19 Jan 2017 06:31:26 GMT

     [ https://issues.apache.org/jira/browse/HDFS-11268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

SammiChen updated HDFS-11268:
    Attachment: HDFS-11268-002.patch

Hi [~andrew.wang]], thanks for reviewing the patch! I rebased it. 

> Correctly reconstruct erasure coding file from FSImage
> ------------------------------------------------------
>                 Key: HDFS-11268
>                 URL: https://issues.apache.org/jira/browse/HDFS-11268
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: erasure-coding
>    Affects Versions: 3.0.0-alpha1
>            Reporter: SammiChen
>            Assignee: SammiChen
>            Priority: Critical
>              Labels: hdfs-ec-3.0-must-do
>         Attachments: HDFS-11268-001.patch, HDFS-11268-002.patch
> Currently, FSImageFormatProtoBuf has the information about whether the file is striped
or not and saved file's erasure coding policy ID in replication field. But later, when FSImage
is loaded to create the name space, the default system erasure coding policy is used to reconstruct
file's block structure.  In case if the erasure coding policy of file is not the default erasure
coding policy, the content of the file cannot be accessed correctly. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message