You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/08/28 18:36:46 UTC
[jira] [Commented] (SPARK-10332) spark-submit to yarn doesn't fail
if executors is 0
[ https://issues.apache.org/jira/browse/SPARK-10332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720201#comment-14720201 ]
Sean Owen commented on SPARK-10332:
-----------------------------------
I think this was changed to allow 0 (could be misremembering this) so you can start with 0 executors and only request them once something needs to do work. However if you're saying executors never get requested, that's a problem of course.
> spark-submit to yarn doesn't fail if executors is 0
> ---------------------------------------------------
>
> Key: SPARK-10332
> URL: https://issues.apache.org/jira/browse/SPARK-10332
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.5.0
> Reporter: Thomas Graves
>
> Running spark-submit with yarn with number-executors equal to 0 when not using dynamic allocation should error out.
> In spark 1.5.0 it continues and ends up hanging.
> yarn.ClientArguments still has the check so something else must have changed.
> spark-submit --master yarn --deploy-mode cluster --class org.apache.spark.examples.SparkPi --num-executors 0 ....
> spark 1.4.1 errors with:
> java.lang.IllegalArgumentException:
> Number of executors was 0, but must be at least 1
> (or 0 if dynamic executor allocation is enabled).
--
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