[
https://issues.apache.org/jira/browse/HDDS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292419#comment-17292419
]
Yiqun Lin commented on HDDS-3816:
---------------------------------
Hi [~umamaheswararao],
{quote}Chunk level metadata
The offset and length of each chunk represents the logical offset relative to
the block instance.
{quote}
I see here we introduced the offset and length for chunk, that's only designed
for the FILE_PER_BLOCK layout, right? Under the layout FILE_PER_BLOCK layout,
one block only has one chunk file. But will we also support the EC chunk write
for another FILE_PER_CHUNK layout in the first phase implementation? We have
two available chunk layout now. And the EC chunk read/write logic should be
different under this two layout.
> 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]
