You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/04/19 17:20:01 UTC
[jira] [Updated] (BEAM-11832) Time correction by NTP sync can skew
metrics
[ https://issues.apache.org/jira/browse/BEAM-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot updated BEAM-11832:
---------------------------------
Labels: stale-P2 (was: )
> Time correction by NTP sync can skew metrics
> --------------------------------------------
>
> Key: BEAM-11832
> URL: https://issues.apache.org/jira/browse/BEAM-11832
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Minbo Bae
> Priority: P2
> Labels: stale-P2
> Attachments: clock_correction.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> GCE VM time can be corrected by NTP sync. If this happens,`System.currentTimeMillis()` can set back to the past. You may see this [^clock_correction.png] in Cloud Logging for time correction.
> The rolled back clock can cause skewed metrics. For example, `ExecutionStateSampler` uses `System.currentTimeMillis` [1]. I guess we can mitigate this issue using `System.nanoTime` for elapsed times (maybe not perfect as per [2]).
> [1] [https://github.com/apache/beam/blob/v2.27.0/runners/core-java/src/main/java/org/apache/beam/runners/core/metrics/ExecutionStateSampler.java#L42]
> [2] [https://bugs.openjdk.java.net/browse/JDK-6458294]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)