You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Manikumar (Jira)" <ji...@apache.org> on 2020/10/31 20:27:00 UTC

[jira] [Created] (KAFKA-10669) ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1

Manikumar created KAFKA-10669:
---------------------------------

             Summary: ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1
                 Key: KAFKA-10669
                 URL: https://issues.apache.org/jira/browse/KAFKA-10669
             Project: Kafka
          Issue Type: Task
    Affects Versions: 2.7.0
            Reporter: Manikumar
             Fix For: 2.7.0


Couple of failures observed after KAFKA-9627: Replace ListOffset request/response with automated protocol ([https://github.com/apache/kafka/pull/8295])

1. Latest consumer fails to consume from 0.10.0.1 brokers. Below system tests are failing
 kafkatest.tests.client.client_compatibility_features_test.ClientCompatibilityFeaturesTest system test failing for "0.10.0.1" broker
 kafkatest.tests.client.client_compatibility_produce_consume_test.ClientCompatibilityProduceConsumeTest

2. In some scenarios, latest consumer fails with below error when connecting to a Kafka cluster which consists of newer and older (<=2.0) Kafka brokers 
 org.apache.kafka.common.errors.UnsupportedVersionException: Attempted to write a non-default currentLeaderEpoch at version 3



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