You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Nishkam Ravi (JIRA)" <ji...@apache.org> on 2015/07/08 02:07:05 UTC
[jira] [Updated] (SPARK-8881) Scheduling fails if num_executors <
num_workers
[ https://issues.apache.org/jira/browse/SPARK-8881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nishkam Ravi updated SPARK-8881:
--------------------------------
Description:
Current scheduling algorithm (in Master.scala) has two issues:
1. cores are allocated one at a time instead of spark.executor.cores at a time
2. when spark.cores.max/spark.executor.cores < num_workers, executors are not launched and the app hangs (due to 1)
was:
Current scheduling algorithm (in Master.scala) has two issues:
(i) cores are allocated one at a time instead of spark.executor.cores at a time
(ii) when spark.cores.max/spark.executor.cores < num_workers, executors are not launched and the app hangs (due to (i))
> Scheduling fails if num_executors < num_workers
> -----------------------------------------------
>
> Key: SPARK-8881
> URL: https://issues.apache.org/jira/browse/SPARK-8881
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 1.4.0, 1.5.0
> Reporter: Nishkam Ravi
>
> Current scheduling algorithm (in Master.scala) has two issues:
> 1. cores are allocated one at a time instead of spark.executor.cores at a time
> 2. when spark.cores.max/spark.executor.cores < num_workers, executors are not launched and the app hangs (due to 1)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org