[jira] [Closed] (FLINK-19174) idleTimeMsPerSecond can report incorrect values (0 or values more than one second)

["Piotr Nowojski (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Nowojski closed FLINK-19174.
----------------------------------
    Fix Version/s: 1.13.0
         Assignee: Piotr Nowojski
       Resolution: Fixed

Merged as 7aafc4c51b0

> 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
>            Assignee: Piotr Nowojski
>            Priority: Minor
>             Fix For: 1.13.0
>
>
> 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)