You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2017/03/09 18:57:38 UTC
[jira] [Resolved] (SPARK-19793) Use clock.getTimeMillis when mark
task as finished in TaskSetManager.
[ https://issues.apache.org/jira/browse/SPARK-19793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcelo Vanzin resolved SPARK-19793.
------------------------------------
Resolution: Fixed
Assignee: jin xing
Fix Version/s: 2.2.0
> Use clock.getTimeMillis when mark task as finished in TaskSetManager.
> ---------------------------------------------------------------------
>
> Key: SPARK-19793
> URL: https://issues.apache.org/jira/browse/SPARK-19793
> Project: Spark
> Issue Type: Bug
> Components: Scheduler
> Affects Versions: 2.1.0
> Reporter: jin xing
> Assignee: jin xing
> Priority: Minor
> Fix For: 2.2.0
>
>
> TaskSetManager is now using *System.getCurrentTimeMillis* when mark task as finished in *handleSuccessfulTask* and *handleFailedTask*. Thus developer cannot set the tasks finishing time in unit test. When *handleSuccessfulTask*, task's duration = System.getCurrentTimeMillis - launchTime(which can be set by *clock*), the result is not correct.
--
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