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

Posted to jira@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2024/08/15 13:59: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=17873967#comment-17873967 ] 

Lianet Magrans commented on KAFKA-16022:
----------------------------------------

I've linked all the jiras that we were causing this error. I think we can close this one since it's only an observation of the error and we've identified the specific issues. We can reopen in the future if needed. 

> 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, kip-848-client-support
>             Fix For: 3.9.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)