[KAFKA-16427] KafkaConsumer#position() does not respect timeout when group protocol is CONSUMER

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.8.0
• Component/s: clients, consumer
• Labels: consumer-threading-refactor timeout
• Assignee: Kirk True
• Reporter: Alyssa Huang
• Reviewer: Bruno Cadonna
• Created: 26/Mar/24 18:12
• Updated: 04/May/24 02:29
• Resolved: 04/May/24 02:29

Description

When

`long position(TopicPartition partition, final Duration timeout);`

is called on an unknown topic partition (and auto creation is disabled), the method fails to adhere to the timeout supplied.

e.g. the following warning is logged continuously as metadata fetches are retried 
[2024-03-26 11:03:48,589] WARN [Consumer clientId=ConsumerTestConsumer, groupId=my-test] Error while fetching metadata with correlation id 200 : {nonexistingTopic=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient:1313)

Issue Links

• is related to: KAFKA-15974 Enforce that event processing respects user-provided timeout
• is related to: KAFKA-16200 Enforce that RequestManager implementations respect user-provided timeout
• links to: GitHub Pull Request #15843