[KAFKA-12272] Kafka Streams metric commit-latency-max and commit-latency-avg is always 0

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7.0, 2.6.1
• Fix Version/s: 2.8.0, 2.7.1, 2.6.2
• Component/s: streams
• Assignee: Matthias J. Sax
• Reporter: Damien Gasparina
• Created: 02/Feb/21 18:08
• Updated: 12/Feb/21 01:00
• Resolved: 12/Feb/21 01:00

Description

After upgrading to Kafka Streams 2.7.0, the JMX metrics commit-latency-max and commit-latency-avg is always equal to 0.

For the same application, with Kafka Streams 2.6.0 and bellow, I can observe:

With Kafka Streams 2.7.0:

By quickly looking at the issue, I got the feeling it's a drawback from: https://github.com/apache/kafka/pull/9634.

We are setting now to the current Time in the maybeCommit() function: https://github.com/apache/kafka/blob/2.7/streams/src/main/java/org/apache/kafka/streams/processor/internals/StreamThread.java#L930.

And just after we do a Time.millisecond() - now (that we just updated) to compute the latency: https://github.com/apache/kafka/blob/2.7/streams/src/main/java/org/apache/kafka/streams/processor/internals/StreamThread.java#L692

Issue Links

• is caused by: KAFKA-10755 Should consider commit latency when computing next commit timestamp
• links to: GitHub Pull Request #10102
• links to: GitHub Pull Request #10103
• links to: GitHub Pull Request #10104