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-7839) Erasure coding: move EC policies from file header to XAttr
Date Fri, 27 Feb 2015 20:42:05 GMT

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

Kai Zheng commented on HDFS-7839:

Thanks [~zhz] for taking care of this.
bq.Should we allow an EC zone to be created under an existing EC zone?
I thought we'd better not support nested EC zone at initial phase. We can leave it for future
consideration when get more thoughts, user experiences and cases about EC zone. Does encryption
zone support nesting ?
bq.Should we allow EC files to exist without a zone?
I thought so. As you said, this would allow files in replication mode not to be affected by
this new feature, which is important to keep compatibility.
I'm glad we have a {{ErasureCodingManager}} to take care of EC zones. Thanks.

> Erasure coding: move EC policies from file header to XAttr
> ----------------------------------------------------------
>                 Key: HDFS-7839
>                 URL: https://issues.apache.org/jira/browse/HDFS-7839
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>         Attachments: HDFS-7839-000.patch, HDFS-7839-001.patch
> As a quick first step to facilitate initial development and testing, HDFS-7347 added
EC configuration in file header as one storage policy. We have discussed and [concluded |https://issues.apache.org/jira/browse/HDFS-7285?focusedCommentId=14296210&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14296210]
that EC configurations should be part of XAttr. This JIRA aims to add the basic EC XAttr structure.
HDFS-7337 will add configurable and pluggable schema info.

This message was sent by Atlassian JIRA

View raw message