[
https://issues.apache.org/jira/browse/TEZ-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224255#comment-17224255
]
László Bodor edited comment on TEZ-2442 at 11/1/20, 2:07 PM:
-------------------------------------------------------------
this still looks interesting, I've refreshed the old patch and uploaded as
[^TEZ-2442.06.patch], in which I resolved the conflicts and adjusted the tests
(the original patch was ~4 years old)
let's wait for some test results before further discussion and cluster testing
was (Author: abstractdog):
this still looks interesting, I've refreshed the old patch and uploaded as
[^TEZ-2442.06.patch], let's wait for some test results before further
discussion and cluster testing
> 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: László Bodor
> Priority: Major
> Attachments: FS_based_shuffle_v2.pdf, TEZ-2442.06.patch, Tez Shuffle
> using DFS.pdf, hdfs_broadcast_hack.txt, tez-2442-trunk.2.patch,
> tez-2442-trunk.3.patch, tez-2442-trunk.4.patch, tez-2442-trunk.5.patch,
> 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
(v8.3.4#803005)
