[
https://issues.apache.org/jira/browse/HDFS-7839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391396#comment-14391396
]
Jing Zhao commented on HDFS-7839:
---------------------------------
Thanks for working on this, Zhe! The patch looks good to me. Some minor
comments:
# The change of log4j.properties can be removed
# Should we disallow setting root as an EC zone?
# I think we can first disallow nested EC zone
# {{getECPolicy}} can take INodesInPath as its parameter.
# We need more unit tests to cover all the zone creation scenarios. Also we
need to test all the restrictions defined by the zone. Also need to make sure
file creation and block allocation recognize the zone (this part may have been
covered by existing tests).
> Erasure coding: implement facilities in NameNode to create and manage EC zones
> ------------------------------------------------------------------------------
>
> 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,
> HDFS-7839-002.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 JIRA will follow the [plan |
> https://issues.apache.org/jira/browse/HDFS-7285?focusedCommentId=14370307&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14370307]
> we made under HDFS-7285.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
