You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "BoYang (Jira)" <ji...@apache.org> on 2020/06/07 06:55:00 UTC
[jira] [Updated] (SPARK-31924) Create remote shuffle service
reference implementation
[ https://issues.apache.org/jira/browse/SPARK-31924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
BoYang updated SPARK-31924:
---------------------------
Description:
People in [Spark Scalability & Reliability Sync Meeting |https://docs.google.com/document/d/1T3y25dOaKWVO0pWd838GeiTeI3DUQJtwy6MKYPLuleg]have discussed a lot about remote (disaggregated) shuffle service, and plan to do a reference implementation to help demonstrate some basic design and pave the way for a future production grade remote shuffle service.
There are already two pull requests to enhance Spark shuffle metadata API to make it easy/possible to implement remote shuffle service ([PR 28616|https://github.com/apache/spark/pull/28616], [PR 28618|https://github.com/apache/spark/pull/28618]). Creating a remote shuffle service reference implementation will help to validate those shuffle metadata API.
was:
People in [Spark Scalability & Reliability Sync Meeting|[https://docs.google.com/document/d/1T3y25dOaKWVO0pWd838GeiTeI3DUQJtwy6MKYPLuleg]] have discussed a lot about remote (disaggregated) shuffle service, and plan to do a reference implementation to help demonstrate some basic design and pave the way for a future production grade remote shuffle service.
There are already two pull requests to enhance Spark shuffle metadata API to make it easy/possible to implement remote shuffle service ([PR 28616|https://github.com/apache/spark/pull/28616], [PR 28618|https://github.com/apache/spark/pull/28618]). Creating a remote shuffle service reference implementation will help to validate those shuffle metadata API.
> Create remote shuffle service reference implementation
> ------------------------------------------------------
>
> Key: SPARK-31924
> URL: https://issues.apache.org/jira/browse/SPARK-31924
> Project: Spark
> Issue Type: New Feature
> Components: Shuffle
> Affects Versions: 3.0.0
> Reporter: BoYang
> Priority: Major
> Fix For: 3.0.0
>
>
> People in [Spark Scalability & Reliability Sync Meeting |https://docs.google.com/document/d/1T3y25dOaKWVO0pWd838GeiTeI3DUQJtwy6MKYPLuleg]have discussed a lot about remote (disaggregated) shuffle service, and plan to do a reference implementation to help demonstrate some basic design and pave the way for a future production grade remote shuffle service.
>
> There are already two pull requests to enhance Spark shuffle metadata API to make it easy/possible to implement remote shuffle service ([PR 28616|https://github.com/apache/spark/pull/28616], [PR 28618|https://github.com/apache/spark/pull/28618]). Creating a remote shuffle service reference implementation will help to validate those shuffle metadata API.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org