[ https://issues.apache.org/jira/browse/SPARK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549956#comment-14549956 ]
Sean Owen commented on SPARK-7699: ---------------------------------- Agree, but this logic change only also happens a bit later. I'm just talking about the case where you are running _some_ load versus _none_. With no or little load, I expect it to show minimum executors quickly rather than what the initial number was. That is, I don't agree that the initial number is not the configured value, but think in your case the initial value is quickly not used anymore. > Config "spark.dynamicAllocation.initialExecutors" has no effect > ---------------------------------------------------------------- > > Key: SPARK-7699 > URL: https://issues.apache.org/jira/browse/SPARK-7699 > Project: Spark > Issue Type: Bug > Components: Spark Core > Reporter: meiyoula > > spark.dynamicAllocation.minExecutors 2 > spark.dynamicAllocation.initialExecutors 3 > spark.dynamicAllocation.maxExecutors 4 > Just run the spark-shell with above configurations, the initial executor > number is 2. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org