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

Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/02/08 14:15:34 UTC

[jira] [Updated] (SPARK-5332) Efficient way to deal with ExecutorLost

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

Sean Owen updated SPARK-5332:
-----------------------------
    Component/s: Spark Core
       Priority: Minor  (was: Major)

> Efficient way to deal with ExecutorLost
> ---------------------------------------
>
>                 Key: SPARK-5332
>                 URL: https://issues.apache.org/jira/browse/SPARK-5332
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Liang-Chi Hsieh
>            Priority: Minor
>
> Currently, the handler of the case when an executor being lost in DAGScheduler (handleExecutorLost) looks not efficient. This pr tries to add a bit of extra information to Stage class to improve that.



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