[
https://issues.apache.org/jira/browse/KAFKA-16022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868135#comment-17868135
]
Lianet Magrans commented on KAFKA-16022:
----------------------------------------
Hey [~phuctran] , there are already 2 tasks for solving known issues leading to
this error: KAFKA-17066 and KAFKA-17064. Those bugs could definitely lead to
this.
> 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.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)
