[
https://issues.apache.org/jira/browse/KAFKA-16427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842817#comment-17842817
]
Kirk True commented on KAFKA-16427:
-----------------------------------
This bug can be triggered with an embarrassingly simple integration test (n)
But it appears this bug can be fixed with an embarrassingly simple change, so
(y)
> KafkaConsumer#position() does not respect timeout when group protocol is
> CONSUMER
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-16427
> URL: https://issues.apache.org/jira/browse/KAFKA-16427
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 3.7.0
> Reporter: Alyssa Huang
> Assignee: Kirk True
> Priority: Critical
> Labels: consumer-threading-refactor, timeout
> Fix For: 3.8.0
>
>
> 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)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
