[
https://issues.apache.org/jira/browse/HDFS-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289209#comment-14289209
]
Li Bo commented on HDFS-7653:
-----------------------------
Thanks for your comments.
I think we probably should separate Readers and Writers in two different JIRAs
for easing the review.
-- Agree. I will separate readers and writers in two jiras later.
For the EC reader, it should implement a new EcDFSInputStream and reuse the
existing hdfs readers in order to have all caching and short circuit read
features.
-- I have implemented a new dfs InputStream(named DFSStripeInputStream) and it
uses ClientBlockReader. ClientBlockReader uses the existing two BlockReader and
can have all caching and short circuit read features. I will upload code to
HDFS-7545 in several days which show the usage of these readers and writers.
> Block Readers and Writers used in both client side and datanode side
> --------------------------------------------------------------------
>
> Key: HDFS-7653
> URL: https://issues.apache.org/jira/browse/HDFS-7653
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Li Bo
> Assignee: Li Bo
> Attachments: BlockReadersWriters.patch
>
>
> There're a lot of block read/write operations in HDFS-EC, for example, when
> client writes a file in striping layout, client has to write several blocks
> to several different datanodes; if a datanode wants to do an
> encoding/decoding task, it has to read several blocks from itself and other
> datanodes, and writes one or more blocks to itself or other datanodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
