You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2019/05/05 08:35:00 UTC

[jira] [Assigned] (SPARK-27603) Make ShuffleClient pluggable

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

Apache Spark reassigned SPARK-27603:
------------------------------------

    Assignee: Apache Spark

> Make ShuffleClient pluggable
> ----------------------------
>
>                 Key: SPARK-27603
>                 URL: https://issues.apache.org/jira/browse/SPARK-27603
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 2.4.0
>            Reporter: Chenzhao Guo
>            Assignee: Apache Spark
>            Priority: Major
>
> ShuffleClient resides in BlockManager, it's the client to read other executors' shuffle files.
> ShuffleManager is pluggable, however, ShuffleClient is restrained to be either a `NettyBlockTransferService` or an `ExternalShuffleClient`(&`MesosExternalShuffleClient`).
> When a custom ShuffleManager is used, the current 3 implementations of ShuffleClient may not be enough. For example, a shuffle manager leveraging remote storage may require the network transferring shuffle data index(the ranges of blocks) from the executor who wrote them, and then read directly from the globally-accessible remote storage, instead of transfering data through network as the 3 implementations do. Also, there is need for non-Netty based block transfer service.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org