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

["Matthias J. Sax (Jira)" <ji...@apache.org>]

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

Matthias J. Sax updated KAFKA-12272:
------------------------------------
    Fix Version/s: 2.6.2
                   2.7.1
                   2.8.0

> Kafka Streams metric commit-latency-max and commit-latency-avg is always 0
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-12272
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12272
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.7.0, 2.6.1
>            Reporter: Damien Gasparina
>            Assignee: Matthias J. Sax
>            Priority: Minor
>             Fix For: 2.8.0, 2.7.1, 2.6.2
>
>         Attachments: KS-2.6.0.png, KS-2.7.0.png
>
>
> 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:
>  !KS-2.6.0.png! 
> With Kafka Streams 2.7.0:
>  !KS-2.7.0.png! 
> 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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)