[
https://issues.apache.org/jira/browse/SPARK-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved SPARK-8974.
------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
1.4.2
Issue resolved by pull request 7352
[https://github.com/apache/spark/pull/7352]
> There is a bug in dynamicAllocation. When there is no running tasks, the
> number of executor a long time without running tasks, the number of executor
> does not reduce to the value of "spark.dynamicAllocation.minExecutors".
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-8974
> URL: https://issues.apache.org/jira/browse/SPARK-8974
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.4.0
> Reporter: KaiXinXIaoLei
> Priority: Minor
> Fix For: 1.4.2, 1.5.0
>
>
> In yarn-client mode and config option "spark.dynamicAllocation.enabled " is
> true, when the state of ApplicationMaster is dead or disconnected, if the
> tasks are submitted before new ApplicationMaster start. The thread of
> spark-dynamic-executor-allocation will throw exception, When
> ApplicationMaster is running and not tasks are running, the number of
> executor is not zero. So feture of dynamicAllocation are not supported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
