GitHub user markgrover opened a pull request:
https://github.com/apache/spark/pull/14223
[SPARK-10614][CORE] SystemClock uses non-monotonic time
## What changes were proposed in this pull request?
Change SystemClock to derive time from System.nanoTime() instead of
System.currentTimeMillis(). This is because using System.currentTimeMillis()
makes waitTillTime() routine brittle against systems like VMs where time can go
forward and backwards.
Shout out to @steveloughran for doing a good chunk of research and a
previous PR (#8766) on this in 2015.
## How was this patch tested?
Build is green, I am running unit tests, they are looking green, but are
also taking a while. So, filing this PR a little proactively.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markgrover/spark SPARK-10614
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/14223.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #14223
----
commit a475cd82455e892b23efe2e8fad0dade2ec8b043
Author: Mark Grover <[email protected]>
Date: 2016-07-14T23:42:39Z
[SPARK-10614][CORE] SystemClock uses non-monotonic time in its wait logic
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
