[
https://issues.apache.org/jira/browse/HDDS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521285#comment-17521285
]
Uma Maheswara Rao G commented on HDDS-3816:
-------------------------------------------
If anybody interested to review the changes, here is the PR:
[https://github.com/apache/ozone/pull/3301]
This does not have https://issues.apache.org/jira/browse/HDDS-5909 and
https://issues.apache.org/jira/browse/HDDS-6209 as they are not in yet.
> Erasure Coding
> --------------
>
> Key: HDDS-3816
> URL: https://issues.apache.org/jira/browse/HDDS-3816
> Project: Apache Ozone
> Issue Type: New Feature
> Components: OM, Ozone Client, Ozone Datanode, SCM
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Priority: Major
> Labels: EC, pull-request-available
> Attachments: Apache Ozone Erasure Coding-V2.pdf,
> EC-read-write-path.pdf, Erasure Coding in Apache Hadoop Ozone.pdf, Ozone EC
> Container groups and instances.pdf, Ozone EC v3.pdf
>
>
> We propose to implement Erasure Coding in Apache Ozone to provide efficient
> storage. With EC in place, Ozone can provide same or better tolerance by
> giving 50% or more storage space savings.
> In HDFS project, we already have native codecs(ISAL) and Java codecs
> implemented, we can leverage the same or similar codec design.
> However, the critical part of EC data layout design is in-progress, we will
> post the design doc soon.
> Also see HDDS-5351, which has a bunch of pre-requisites for the EC feature
> committed directly to the {{master}} branch.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
