[ 
https://issues.apache.org/jira/browse/HDFS-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005479#comment-16005479
 ] 

Kai Zheng commented on HDFS-7859:
---------------------------------

As there are particular interests and requirements to support more codecs and 
coders, like in HDFS-11503; and we received user queries regarding how to try 
their own EC policies like using different cell size. So accordingly we want to 
solve this and make a further step in HDFS-7337 to support pluggable and 
configurable codecs. The design doc was updated with latest discussions and 
related work, which I hope can address the design level questions that's 
already raised or will be raised here. 

[~szetszwo], per your request this should be proceeded with design since it's 
to change the fsimage, which is why I want to ping you. Would you let me know 
if you have any concerns or would confirm. I know you're very busy with Ozone, 
so thanks for your time :)!

> 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: SammiChen
>         Attachments: HDFS-7859.001.patch, HDFS-7859.002.patch, 
> HDFS-7859.004.patch, HDFS-7859.005.patch, HDFS-7859.006.patch, 
> HDFS-7859.007.patch, HDFS-7859.008.patch, HDFS-7859.009.patch, 
> HDFS-7859.010.patch, HDFS-7859-HDFS-7285.002.patch, 
> HDFS-7859-HDFS-7285.002.patch, HDFS-7859-HDFS-7285.003.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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to