You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Phuc Hong Tran (Jira)" <ji...@apache.org> on 2024/01/17 06:58:00 UTC

[jira] [Commented] (KAFKA-16022) AsyncKafkaConsumer sometimes complains “No current assignment for partition {}”

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

Phuc Hong Tran commented on KAFKA-16022:
----------------------------------------

[~pnee], were you seeing this exception in the FetchRequestManagerTest or was it some places else?

> AsyncKafkaConsumer sometimes complains “No current assignment for partition {}”
> -------------------------------------------------------------------------------
>
>                 Key: KAFKA-16022
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16022
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>            Reporter: Philip Nee
>            Assignee: Phuc Hong Tran
>            Priority: Minor
>              Labels: consumer-threading-refactor
>             Fix For: 3.8.0
>
>
> This seems to be a timing issue that before the member receives any assignment from the coordinator, the fetcher will try to find the current position causing "No current assignment for partition {}".  This creates a small amount of noise to the log.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)