You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2017/03/09 18:56:38 UTC
[jira] [Updated] (SPARK-19757) Executor with task scheduled could
be killed due to idleness
[ https://issues.apache.org/jira/browse/SPARK-19757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcelo Vanzin updated SPARK-19757:
-----------------------------------
Reporter: jin xing (was: Jimmy Xiang)
> Executor with task scheduled could be killed due to idleness
> ------------------------------------------------------------
>
> Key: SPARK-19757
> URL: https://issues.apache.org/jira/browse/SPARK-19757
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.6.0
> Reporter: jin xing
> Assignee: Jimmy Xiang
> Priority: Minor
> Fix For: 2.2.0
>
>
> With dynamic executor allocation enabled on yarn mode, after one job is finished for a while, submit another job, then there is race between killing idle executors and scheduling new task on these executors. Sometimes, some executor is killed right after a task is scheduled on it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org