[jira] [Updated] (KAFKA-7535) KafkaConsumer doesn't report records-lag if isolation.level is read_committed

["Ismael Juma (JIRA)" <ji...@apache.org>]

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

Ismael Juma updated KAFKA-7535:
-------------------------------
    Fix Version/s: 2.0.2
                   2.1.1

> KafkaConsumer doesn't report records-lag if isolation.level is read_committed
> -----------------------------------------------------------------------------
>
>                 Key: KAFKA-7535
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7535
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 2.0.0
>            Reporter: Alexey Vakhrenev
>            Assignee: lambdaliu
>            Priority: Major
>              Labels: regression
>             Fix For: 2.1.1, 2.0.2
>
>
> Starting from 2.0.0, {{KafkaConsumer}} doesn't report {{records-lag}} if {{isolation.level}} is {{read_committed}}. The last version, where it works is {{1.1.1}}.
> The issue can be easily reproduced in {{kafka.api.PlaintextConsumerTest}} by adding {{consumerConfig.setProperty("isolation.level", "read_committed")}} witin related tests:
>  - {{testPerPartitionLagMetricsCleanUpWithAssign}}
>  - {{testPerPartitionLagMetricsCleanUpWithSubscribe}}
>  - {{testPerPartitionLagWithMaxPollRecords}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)