[
https://issues.apache.org/jira/browse/SPARK-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119365#comment-14119365
]
Mridul Muralidharan commented on SPARK-3019:
--------------------------------------------
I will try to push the version we had last worked on for 2G fix (a pre-1.1
fork) to git later today/this week - and we can take a look at it.
It might require some effort to rebase it to 1.1 since it is slightly dated;
but that can be done if required : the main reason for the push would be to
illustrate the reason why the interfaces exist in SPARK-1476 and how they are
used : so that there is a better understanding of the required functional
change.
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
