You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Saisai Shao (JIRA)" <ji...@apache.org> on 2016/02/23 08:17:18 UTC
[jira] [Updated] (SPARK-13447) Fix AM failure situation for dynamic
allocation diabled situation
[ https://issues.apache.org/jira/browse/SPARK-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saisai Shao updated SPARK-13447:
--------------------------------
Summary: Fix AM failure situation for dynamic allocation diabled situation (was: Fix AM failure situation for dynamic allocation diabled sitation)
> Fix AM failure situation for dynamic allocation diabled situation
> -----------------------------------------------------------------
>
> Key: SPARK-13447
> URL: https://issues.apache.org/jira/browse/SPARK-13447
> Project: Spark
> Issue Type: Bug
> Components: Spark Core, YARN
> Affects Versions: 1.6.0
> Reporter: Saisai Shao
>
> Because of lag of executor disconnection events, stale states in the {{CoarseGrainedSchedulerBacked}} will ruin the newly registered executor information. This situation is handled for dynamic allocation enabled situation, for dynamic allocation disabled scenario, we should also have the similar fix.
--
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