[ https://issues.apache.org/jira/browse/SPARK-10614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379801#comment-15379801 ]
Apache Spark commented on SPARK-10614: -------------------------------------- User 'markgrover' has created a pull request for this issue: https://github.com/apache/spark/pull/14223 > 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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org