You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2014/08/14 08:41:12 UTC
[jira] [Commented] (SPARK-3019) Pluggable block transfer (data
plane communication) interface
[ https://issues.apache.org/jira/browse/SPARK-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096654#comment-14096654 ]
Hari Shreedharan commented on SPARK-3019:
-----------------------------------------
Why specifically MapR FS? You could use HDFS for this as well right?
> Pluggable block transfer (data plane communication) interface
> -------------------------------------------------------------
>
> Key: SPARK-3019
> URL: https://issues.apache.org/jira/browse/SPARK-3019
> Project: Spark
> Issue Type: Improvement
> Components: Shuffle, Spark Core
> Reporter: Reynold Xin
> Assignee: Reynold Xin
> Attachments: PluggableBlockTransferServiceProposalforSpark - draft 1.pdf
>
>
> The attached design doc proposes a standard interface for block transferring, which will make future engineering of this functionality easier, allowing the Spark community to provide alternative implementations.
> Block transferring is a critical function in Spark. All of the following depend on it:
> * shuffle
> * torrent broadcast
> * block replication in BlockManager
> * remote block reads for tasks scheduled without locality
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org