[
https://issues.apache.org/jira/browse/FLINK-20829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258078#comment-17258078
]
Till Rohrmann commented on FLINK-20829:
---------------------------------------
Thanks for reporting this issue [~yuyang08]. I think the problem has been fixed
with FLINK-19009.
> flink.jm.downtime metric is inaccurate in flink 1.9.1 and 1.11.1
> ----------------------------------------------------------------
>
> Key: FLINK-20829
> URL: https://issues.apache.org/jira/browse/FLINK-20829
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Metrics
> Affects Versions: 1.9.1, 1.11.1
> Reporter: Yu Yang
> Priority: Major
> Attachments: Screen Shot 2021-01-01 at 2.38.39 PM.png
>
>
> According to the comments in
> [DownTimeGauge.java|https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/metrics/DownTimeGauge.java#L28]:
>
> A gauge that returns (in milliseconds) how long a job has not been not
> running any more, in case it is in a failing/recovering situation. Running
> jobs return naturally a value of zero.
>
> We noticed that flink runtime reports inaccurate value for flink.jm.downtime
> metric. What flink reports was actually the uptime in milliseconds before
> the application restarted.
>
> !Screen Shot 2021-01-01 at 2.38.39 PM.png|width=720!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
