[ https://issues.apache.org/jira/browse/KAFKA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662812#comment-16662812 ]
Ismael Juma commented on KAFKA-7535: ------------------------------------ cc [~lindong] [~omkreddy] in case you think this is important enough to include in 2.01/2.1.0. It's a regression, but I haven't verified the severity aside from the consumer lag issue. > 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)