[
https://issues.apache.org/jira/browse/KAFKA-16315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872512#comment-17872512
]
Colin McCabe commented on KAFKA-16315:
--------------------------------------
Moving to 4.0 since feature freeze has come and gone for 3.9.
> Investigate propagating metadata updates via queues
> ---------------------------------------------------
>
> Key: KAFKA-16315
> URL: https://issues.apache.org/jira/browse/KAFKA-16315
> Project: Kafka
> Issue Type: Task
> Components: clients, consumer
> Affects Versions: 3.7.0
> Reporter: Kirk True
> Priority: Major
> Labels: consumer-threading-refactor
> Fix For: 4.0.0
>
>
> Some of the new {{AsyncKafkaConsumer}} logic enqueues events for the network
> I/O thread then issues a call to update the {{ConsumerMetadata}} via
> {{requestUpdate()}}. If the event ends up stuck in the queue for a long time,
> it is possible that the metadata is not updated at the correct time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
