[
https://issues.apache.org/jira/browse/HDFS-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245203#comment-15245203
]
Zhe Zhang commented on HDFS-7859:
---------------------------------
Thanks Kia and Rakesh for reactivating the discussion.
I agree that at this stage there isn't a clear need for custom policies.
The main motivation for persisting EC policies in NN is probably downgrade.
Assuming that we never remove any existing built-in policies from
{{ErasureCodingPolicyManager}}, we won't have issues with upgrade. But the
chance of adding an EC policy in a 3.x release is nontrivial.
So I don't think this is a 3.0 blocker. But it would be nice to have it for 3.0
release.
> Erasure Coding: Persist erasure coding policies in NameNode
> -----------------------------------------------------------
>
> Key: HDFS-7859
> URL: https://issues.apache.org/jira/browse/HDFS-7859
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Xinwei Qin
> Labels: BB2015-05-TBR
> Attachments: HDFS-7859-HDFS-7285.002.patch,
> HDFS-7859-HDFS-7285.002.patch, HDFS-7859-HDFS-7285.003.patch,
> HDFS-7859.001.patch, HDFS-7859.002.patch
>
>
> In meetup discussion with [~zhz] and [~jingzhao], it's suggested that we
> persist EC schemas in NameNode centrally and reliably, so that EC zones can
> reference them by name efficiently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
