You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "shanyu zhao (JIRA)" <ji...@apache.org> on 2016/04/16 10:30:25 UTC

[jira] [Updated] (TEZ-2442) Support DFS based shuffle in addition to HTTP shuffle

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

shanyu zhao updated TEZ-2442:
-----------------------------
    Attachment: tez-2442-trunk.patch
                FS_based_shuffle_v2.pdf

Updated design doc FS_based_shuffle_v2.pdf. Added a section on how to clean the intermediate shuffle data.

Patch attached: tez-2442-trunk.patch

> Support DFS based shuffle in addition to HTTP shuffle
> -----------------------------------------------------
>
>                 Key: TEZ-2442
>                 URL: https://issues.apache.org/jira/browse/TEZ-2442
>             Project: Apache Tez
>          Issue Type: Improvement
>    Affects Versions: 0.5.3
>            Reporter: Kannan Rajah
>            Assignee: Kannan Rajah
>         Attachments: FS_based_shuffle_v2.pdf, Tez Shuffle using DFS.pdf, hdfs_broadcast_hack.txt, tez-2442-trunk.patch, tez_hdfs_shuffle.patch
>
>
> In Tez, Shuffle is a mechanism by which intermediate data can be shared between stages. Shuffle data is written to local disk and fetched from any remote node using HTTP. A DFS like MapR file system can support writing this shuffle data directly to its DFS using a notion of local volumes and retrieve it using HDFS API from remote node. The current Shuffle implementation assumes local data can only be managed by LocalFileSystem. So it uses RawLocalFileSystem and LocalDirAllocator. If we can remove this assumption and introduce an abstraction to manage local disks, then we can reuse most of the shuffle logic (store, sort) and inject a HDFS API based retrieval instead of HTTP.



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