[
https://issues.apache.org/jira/browse/SPARK-24942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840913#comment-17840913
]
Dongjoon Hyun commented on SPARK-24942:
---------------------------------------
I removed the outdated target version, `3.2.0`, from this Jira. For now, Apache
Spark community has no target version for this issue.
> Improve cluster resource management with jobs containing barrier stage
> ----------------------------------------------------------------------
>
> Key: SPARK-24942
> URL: https://issues.apache.org/jira/browse/SPARK-24942
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.1.0
> Reporter: Xingbo Jiang
> Priority: Major
>
> https://github.com/apache/spark/pull/21758#discussion_r205652317
> We shall improve cluster resource management to address the following issues:
> - With dynamic resource allocation enabled, it may happen that we acquire
> some executors (but not enough to launch all the tasks in a barrier stage)
> and later release them due to executor idle time expire, and then acquire
> again.
> - There can be deadlock with two concurrent applications. Each application
> may acquire some resources, but not enough to launch all the tasks in a
> barrier stage. And after hitting the idle timeout and releasing them, they
> may acquire resources again, but just continually trade resources between
> each other.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
