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

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.11.2, 1.12.0
• Fix Version/s: 1.13.0
• Component/s: Runtime / Metrics
• Assignee: Piotr Nowojski
• Reporter: Piotr Nowojski
• Created: 09/Sep/20 14:45
• Updated: 25/Aug/22 11:55
• Resolved: 06/Jan/21 07:51

Description

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.

Issue Links

• is duplicated by: FLINK-29106 value of metric 'idleTimeMsPerSecond' more than 1000