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

• Type: Task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.7.0
• Assignee: Manikumar
• Reporter: Manikumar
• Created: 31/Oct/20 20:26
• Updated: 03/Nov/20 14:18
• Resolved: 02/Nov/20 18:09

Description

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

Issue Links

• links to: GitHub Pull Request #9540