[
https://issues.apache.org/jira/browse/HDFS-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816802#comment-15816802
]
Andrew Wang commented on HDFS-8095:
-----------------------------------
Got it, thanks for the context Kai. When you say data corruption, do you mean
data loss if the cluster has insufficient # datanodes or racks?
Overall I like the idea of making this act like the blocksize and replication
factor. These are specified by the client and have default values in client
configuration, but the NN enforces limits on the values to make sure they're
reasonable.
Seems related to HDFS-7859. Admins would add all the allowable EC policies, and
users would can choose among them. NN would throw an error if an unknown policy
is requested.
> Allow to configure the system default EC schema
> -----------------------------------------------
>
> Key: HDFS-8095
> URL: https://issues.apache.org/jira/browse/HDFS-8095
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Kai Zheng
> Labels: hdfs-ec-3.0-nice-to-have
>
> As suggested by [~umamaheswararao] and [~vinayrpet] in HDFS-8074, we may
> desire allowing to configure the system default EC schema, so in any
> deployment a cluster admin may be able to define their own system default
> one. In the discussion, we have two approaches to configure the system
> default schema: 1) predefine it in the {{ecschema-def.xml}} file, making sure
> it's not changed; 2) configure the key parameter values as properties in
> {{core-site.xml}}. Open this for future consideration in case it's forgotten.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
