[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=17873970#comment-17873970 ] Phuc Hong Tran commented on KAFKA-16022: Understood. Thanks [~lianetm] > 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 >Affects Versions: 3.7.0, 3.8.0, 3.7.1, 3.9.0 >Reporter: Philip Nee >Priority: Minor > Labels: consumer-threading-refactor, kip-848-client-support > Fix For: 4.0.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)
[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)
[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=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)
[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=17842730#comment-17842730 ] Philip Nee commented on KAFKA-16022: hi [~phuctran] - I believe this came up during integration testing. You can try to see if the fetch request manager test also emits this error. > 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)
[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=17831030#comment-17831030 ] Kirk True commented on KAFKA-16022: --- [~pnee]—can you follow up on [~phuctran]'s question. Thanks! > 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)
[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)