[
https://issues.apache.org/jira/browse/FLINK-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198207#comment-17198207
]
Andrey Zagrebin commented on FLINK-4421:
----------------------------------------
thanks for the input [~sewen]
FLINK-4423 also mentions job status timestamps for REST and logging.
For what I see we still use currentTimeMillis in
ExecutionGraph::transitionState. It sounds reasonable but not sure how it is
important for users.
> Make clocks and time measurements monotonous
> --------------------------------------------
>
> Key: FLINK-4421
> URL: https://issues.apache.org/jira/browse/FLINK-4421
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Stephan Ewen
> Priority: Minor
>
> Currently, many places use {{System.currentTimeMillis()}} to acquire
> timestamps or measure time intervals.
> Since this relies on the system clock, and the system clock is not
> necessarily monotonous (in the presence of clock updates), this can lead to
> negative duration and decreasing timestamps where increasing timestamps are
> expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
