[
https://issues.apache.org/jira/browse/SPARK-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101767#comment-14101767
]
Reynold Xin commented on SPARK-3019:
------------------------------------
Also the rebalance of blocks and that should be delegated to a level above the
block transfer interface. This interface is very simple: it handles
fetching/receiving of blocks. Everything else should be kept out of it for
separation of concerns.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
