[
https://issues.apache.org/jira/browse/SPARK-27665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932823#comment-16932823
]
koert kuipers commented on SPARK-27665:
---------------------------------------
i am a little nervous that this got merged into master without resolving the
blocker SPARK-27780
currently this means spark 3.x will not be able to support dynamic allocation
at all on yarn clusters that have spark 2 shuffle managers installed, which is
all our client clusters pretty much.
> Split fetch shuffle blocks protocol from OpenBlocks
> ---------------------------------------------------
>
> Key: SPARK-27665
> URL: https://issues.apache.org/jira/browse/SPARK-27665
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.4.0
> Reporter: Yuanjian Li
> Assignee: Yuanjian Li
> Priority: Major
> Fix For: 3.0.0
>
>
> As the current approach in OneForOneBlockFetcher, we reuse the OpenBlocks
> protocol to describe the fetch request for shuffle blocks, and it causes the
> extension work for shuffle fetching like SPARK-9853 and SPARK-25341 very
> awkward. We need a new protocol only for shuffle blocks fetcher.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
