You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Andrew Or (JIRA)" <ji...@apache.org> on 2016/03/29 02:04:25 UTC

[jira] [Resolved] (SPARK-13447) Fix AM failure situation for dynamic allocation disabled situation

     [ https://issues.apache.org/jira/browse/SPARK-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Or resolved SPARK-13447.
-------------------------------
          Resolution: Fixed
            Assignee: Saisai Shao
       Fix Version/s: 2.0.0
    Target Version/s: 2.0.0

> Fix AM failure situation for dynamic allocation disabled 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
>            Assignee: Saisai Shao
>             Fix For: 2.0.0
>
>
> 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