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

["Manikumar (Jira)" <ji...@apache.org>]

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

Manikumar resolved KAFKA-10669.
-------------------------------
    Resolution: Fixed

Issue resolved by pull request 9540
[https://github.com/apache/kafka/pull/9540]

> 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
>            Priority: Blocker
>             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
>  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)