GitHub user steveloughran opened a pull request:
https://github.com/apache/spark/pull/8766
SPARK-10614 SystemClock uses non-monotonic time in its wait logic. Thâ¦
This patch adds a new subclass, `MonotonicClock`, and switches
`ExecutorAllocationManager` to using it (it used to use `System.nanoTime()`).
A lot of the code which uses SystemClock would appear to benefit from
moving to a monotonic clock âbut that would a more significant piece of work,
needing understanding of what's happening. Furthermore, some of the uses are of
fields which may also be converted to human-formatted time; the nanotime clock
shouldn't be used that way.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/steveloughran/spark
stevel/feature/SPARK-10614-monotonic-time
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/8766.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 #8766
----
commit a71af05053f4f32a5782ef6f4d3518ad2dbfbe27
Author: Steve Loughran <[email protected]>
Date: 2015-09-15T10:11:44Z
SPARK-10614 SystemClock uses non-monotonic time in its wait logic. This
patch adds a new subclass, MonotonicClock, and switches
ExecutorAllocationManager to using it (it used to use System.nanoTime())
----
---
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]
