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

Posted to issues@spark.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/09/15 10:45:46 UTC

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

Steve Loughran created SPARK-10614:
--------------------------------------

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


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
(v6.3.4#6332)

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