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

Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2019/10/15 02:39:00 UTC

[jira] [Resolved] (SPARK-10614) SystemClock uses non-monotonic time in its wait logic

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

Dongjoon Hyun resolved SPARK-10614.
-----------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Issue resolved by pull request 26058
[https://github.com/apache/spark/pull/26058]

> SystemClock uses non-monotonic time in its wait logic
> -----------------------------------------------------
>
>                 Key: SPARK-10614
>                 URL: https://issues.apache.org/jira/browse/SPARK-10614
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.3.0
>            Reporter: Steve Loughran
>            Assignee: Marcelo Masiero Vanzin
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> The consolidated (SPARK-4682) clock uses {{System.currentTimeMillis()}} for measuring time, which means its {{waitTillTime()}} routine is brittle against systems (VMs in particular) whose time can go backwards as well as forward.
> For the {{ExecutorAllocationManager}} this appears to be a regression.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org