You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "SammiChen (JIRA)" <ji...@apache.org> on 2017/01/19 06:32:27 UTC

[jira] [Comment Edited] (HDFS-11268) Correctly reconstruct erasure coding file from FSImage

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

SammiChen edited comment on HDFS-11268 at 1/19/17 6:31 AM:
-----------------------------------------------------------

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


was (Author: sammi):
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
(v6.3.4#6332)

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