spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-19793) Use clock.getTimeMillis when mark task as finished in TaskSetManager.
Date Thu, 02 Mar 2017 09:37:45 GMT

    [ https://issues.apache.org/jira/browse/SPARK-19793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891924#comment-15891924
] 

Apache Spark commented on SPARK-19793:
--------------------------------------

User 'jinxing64' has created a pull request for this issue:
https://github.com/apache/spark/pull/17133

> 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
>            Priority: Minor
>
> 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


Mime
View raw message