[
https://issues.apache.org/jira/browse/HDDS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292691#comment-17292691
]
Marton Elek commented on HDDS-3816:
-----------------------------------
Good question. I think today we have the same "logical" offset related to the
block. This offset may or may not be used by a chunk layout implementation. EC
suggested to use the same approach. We have a logical offset, therefore both
layout can be supported.
It's another question that the logical offset couldn't be mapped back to a
block level offset one by one. During the tradition write, logical offset 1234
is mapped to block offset 1234. While with EC logical offset 1234 is mapped to
something else based on the EC scheme.
> 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
> 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 Hadoop 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
