[
https://issues.apache.org/jira/browse/FLINK-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski updated FLINK-19174:
-----------------------------------
Summary: idleTimeMsPerSecond can report incorrect values (0 or values more
than one second) (was: idleTimeMsPerSecond can report incorrect values if task
is blocked for more then 60 seconds)
> idleTimeMsPerSecond can report incorrect values (0 or values more than one
> second)
> ----------------------------------------------------------------------------------
>
> Key: FLINK-19174
> URL: https://issues.apache.org/jira/browse/FLINK-19174
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Metrics
> Affects Versions: 1.12.0, 1.11.2
> Reporter: Piotr Nowojski
> Priority: Major
>
> If task is blocked for more than 60 seconds
> ({{org.apache.flink.metrics.MeterView#DEFAULT_TIME_SPAN_IN_SECONDS}}),
> {{idleTimeMsPerSecond}} can be reported as zero, despite task being
> completely idle. Once the task is unblocked and the {{idleTimeMsPerSecond}}
> metric is updated, it can for the next 60 seconds exceed 1000ms/second.
> Average value over the longer periods of time will be correct and accurate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
