You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "liuxian (JIRA)" <ji...@apache.org> on 2017/11/28 11:07:00 UTC

[jira] [Created] (SPARK-22628) Some situations, the assignment of executors on workers is not what we expected when `spark.deploy.spreadOut=true`.

liuxian created SPARK-22628:
-------------------------------

             Summary: Some situations,  the assignment of executors on workers is not what we expected when `spark.deploy.spreadOut=true`.
                 Key: SPARK-22628
                 URL: https://issues.apache.org/jira/browse/SPARK-22628
             Project: Spark
          Issue Type: Bug
          Components: Spark Core
    Affects Versions: 2.3.0
            Reporter: liuxian


For example, cluster has 3 workers(workA, workB, workC),  workA has 1 core left, workB has 1 core left, workC has no cores left.
User requests 3 executors (spark.cores.max = 3, spark.executor.cores = 1), obviously, workA  will be assigned one executor ,and workB will be assigned one executor.
After a moment,if some apps release  cores, and workB has 3 core left, workC has 2 core left, we should assign one executor on workC,not workB.

Especially for dynamic executors allocation in standalone mode, this problem is more serious.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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