You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Alexey Vakhrenev (JIRA)" <ji...@apache.org> on 2018/10/23 16:17:00 UTC

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

Alexey Vakhrenev created KAFKA-7535:
---------------------------------------

             Summary: 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


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)