[
https://issues.apache.org/jira/browse/HDFS-11314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-11314:
-------------------------------
Attachment: HDFS-11314.003.patch
Patch attached. Here's a summary of changes:
* Differentiate "system" from "enabled" policies. This meant renaming "active"
to "enabled" in some APIs, comments, variable names.
* Update documentation to talk about EC policies as a concept, and how to
enable them.
* Exception and other messages telling the user how to enable EC policies.
* Update tests to enable additional policies where required.
One question for reviewers is whether we should have a default policy enabled
or not. The set of enabled policies has to be configured correctly for the
cluster at hand, so it might be better to leave it empty and force users to
choose the right value. This would require some more test updates, so I might
ask to do that as a follow-on change.
> Enforce set of enabled EC policies on the NameNode
> --------------------------------------------------
>
> Key: HDFS-11314
> URL: https://issues.apache.org/jira/browse/HDFS-11314
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: erasure-coding
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Priority: Blocker
> Labels: hdfs-ec-3.0-must-do
> Attachments: HDFS-11314.001.patch, HDFS-11314.002.patch,
> HDFS-11314.003.patch
>
>
> Filing based on discussion in HDFS-8095. A user might specify a policy that
> is not appropriate for the cluster, e.g. a RS (10,4) policy when the cluster
> only has 10 nodes. The NN should only allow the client to choose from a
> pre-approved list determined by the cluster administrator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
