[
https://issues.apache.org/jira/browse/HDFS-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179541#comment-15179541
]
Rui Li commented on HDFS-7866:
------------------------------
Thanks Zhe for your comments.
1. We're using 11 bits to store the policy ID, which means it could excess a
byte (replication factor is also a short). What do you think?
2. This is to make the tests use the new policy to find any potential issues.
If there's no further comments, I'll revert it to RS-6-3 in next update. I also
would like to know your opinions about randomly choosing a policy in the tests.
You can refer to my previous
[discussions|https://issues.apache.org/jira/browse/HDFS-7866?focusedCommentId=15171320&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15171320]
with Kai.
3. I agree we can do this in a follow-on. I think essentially it's hacky
because we allow user to specify the replication factor when creating a file
but then overwrite it to store the EC policy ID. Fixing this requires changing
the API, which I think is unacceptable.
> Erasure coding: NameNode manages multiple erasure coding policies
> -----------------------------------------------------------------
>
> Key: HDFS-7866
> URL: https://issues.apache.org/jira/browse/HDFS-7866
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Rui Li
> Attachments: HDFS-7866-v1.patch, HDFS-7866-v2.patch,
> HDFS-7866-v3.patch, HDFS-7866.10.patch, HDFS-7866.11.patch,
> HDFS-7866.4.patch, HDFS-7866.5.patch, HDFS-7866.6.patch, HDFS-7866.7.patch,
> HDFS-7866.8.patch, HDFS-7866.9.patch
>
>
> This is to extend NameNode to load, list and sync predefine EC schemas in
> authorized and controlled approach. The provided facilities will be used to
> implement DFSAdmin commands so admin can list available EC schemas, then
> could choose some of them for target EC zones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
