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

Posted to issues@spark.apache.org by "Adam Kramer (JIRA)" <ji...@apache.org> on 2017/01/27 00:54:24 UTC

[jira] [Updated] (SPARK-19379) SparkAppHandle.getState not registered FAILED state upon Spark app failure in Local mode

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

Adam Kramer updated SPARK-19379:
--------------------------------
    Affects Version/s: 2.1.0

> SparkAppHandle.getState not registered FAILED state upon Spark app failure in Local mode
> ----------------------------------------------------------------------------------------
>
>                 Key: SPARK-19379
>                 URL: https://issues.apache.org/jira/browse/SPARK-19379
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.0.1, 2.1.0
>            Reporter: Adam Kramer
>            Priority: Blocker
>
> LocalSchedulerBackend does not handle calling back to the Launcher upon TaskState change. It does send a callback to setState to FINISHED upon stop(). Apps that are FAILED are set as FINISHED in SparkAppHandle.State.
> It looks like a case statement is needed in the statusUpdate() method in LocalSchedulerBacked to call stop( state) or  launcherBackend.setState(state) with the appropriate SparkAppHandle.State for TaskStates FAILED, LAUNCHING, and, possibly, FINISHED.



--
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