spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kay Ousterhout (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-19398) Log in TaskSetManager is not correct
Date Mon, 06 Feb 2017 18:53:41 GMT

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

Kay Ousterhout resolved SPARK-19398.
------------------------------------
    Resolution: Fixed
      Assignee: jin xing

> Log in TaskSetManager is not correct
> ------------------------------------
>
>                 Key: SPARK-19398
>                 URL: https://issues.apache.org/jira/browse/SPARK-19398
>             Project: Spark
>          Issue Type: Improvement
>          Components: Scheduler
>    Affects Versions: 2.1.0
>            Reporter: jin xing
>            Assignee: jin xing
>            Priority: Trivial
>
> Log below is misleading:
> {code:title="TaskSetManager.scala"}
>     if (successful(index)) {
>       logInfo(
>         s"Task ${info.id} in stage ${taskSet.id} (TID $tid) failed, " +
>         "but another instance of the task has already succeeded, " +
>         "so not re-queuing the task to be re-executed.")
>     }
> {code}
> If fetch failed, the task is marked as *successful* in *TaskSetManager:: handleFailedTask*.
Then log above will be printed. The *successful* just means task will not be scheduled any
longer, not a real success.  



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


Mime
View raw message