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

Youwei Wang updated HDFS-8957:
------------------------------
    Attachment: HDFS-8957.v3.patch

Note: this patch is based on the Hadoop trunk.

Corresponding commitid is:
commit 7992c0b42ceb10fd3ca6c4ced4f59b8e8998e046
Author: Karthik Kambatla <ka...@cloudera.com>
Date:   Tue Aug 9 16:50:57 2016 -0700


> Consolidate client striping input stream codes for stateful read and 
> positional read
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-8957
>                 URL: https://issues.apache.org/jira/browse/HDFS-8957
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: erasure-coding
>            Reporter: Kai Zheng
>            Assignee: Youwei Wang
>         Attachments: HDFS-8957-v1.patch, HDFS-8957.v2.patch, 
> HDFS-8957.v3.patch
>
>
> Currently we have different implementations for client striping read, having 
> both *StatefulStripeReader* and *PositionStripeReader*. I attempted to 
> consolidate the two implementations into one, and it results in much simpler 
> codes, and also better performance. Now in both read paths, it will:
> * Use pooled ByteBuffers, as currently stateful read does;
> * Read directly into application's buffer, as currently positional read does;
> * Try to align and merge multiple stripes, as currently positional read does;
> * Use *ECChunk* version decode API.
> The resultant *StripeReader* is approaching very near now to the ideal state 
> desired by next step, employing *ErasureCoder* API instead of 
> *RawErasureCoder* API.
> Will upload an initial patch to illustrate the rough change, even though it 
> depends on other issues.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to