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

Posted to issues@spark.apache.org by "Jiang Xingbo (JIRA)" <ji...@apache.org> on 2018/07/27 03:46:00 UTC

[jira] [Created] (SPARK-24942) Improve cluster resource management with jobs containing barrier stage

Jiang Xingbo created SPARK-24942:
------------------------------------

             Summary: 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.0.0
            Reporter: Jiang Xingbo


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
(v7.6.3#76005)

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