You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2024/04/02 20:23:00 UTC

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

    [ https://issues.apache.org/jira/browse/KAFKA-16427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833307#comment-17833307 ] 

Kirk True commented on KAFKA-16427:
-----------------------------------

[~alyssahuang]—any chance you have a test case to trigger this, such as an integration or system test? Thanks!

> 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)