[ 
https://issues.apache.org/jira/browse/HDFS-8833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhe Zhang updated HDFS-8833:
----------------------------
    Attachment: HDFS-8833-HDFS-7285.04.patch

Thanks Rakesh for the comment! Actually we are all in sync w.r.t the design, 
including the non-empty dir policy.

So I'm still waiting for Jenkins to verify my latest 'git merge'. While waiting 
I created the 04 patch based on the merged local branch. In case anyone wants 
to review the patch before I update the main feature branch, please use my 
personal github [repo | https://github.com/zhe-thoughts/hadoop/tree/HDFS-7285].

The new patch fixes the test issue Rakesh pointed out. It also reflects 
Walter's comment to avoid renaming {{isStriped}} bit in the file header. We 
probly should keep the bit and reuse the {{REPLICATION}} bits anyway, as I 
proposed above.

> Erasure coding: store EC schema and cell size in INodeFile and eliminate 
> notion of EC zones
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-8833
>                 URL: https://issues.apache.org/jira/browse/HDFS-8833
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: HDFS-7285
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>         Attachments: HDFS-8833-HDFS-7285-merge.00.patch, 
> HDFS-8833-HDFS-7285-merge.01.patch, HDFS-8833-HDFS-7285.02.patch, 
> HDFS-8833-HDFS-7285.03.patch, HDFS-8833-HDFS-7285.04.patch
>
>
> We have [discussed | 
> https://issues.apache.org/jira/browse/HDFS-7285?focusedCommentId=14357754&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14357754]
>  storing EC schema with files instead of EC zones and recently revisited the 
> discussion under HDFS-8059.
> As a recap, the _zone_ concept has severe limitations including renaming and 
> nested configuration. Those limitations are valid in encryption for security 
> reasons and it doesn't make sense to carry them over in EC.
> This JIRA aims to store EC schema and cell size on {{INodeFile}} level. For 
> simplicity, we should first implement it as an xattr and consider memory 
> optimizations (such as moving it to file header) as a follow-on. We should 
> also disable changing EC policy on a non-empty file / dir in the first phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to