Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.7.0
Description
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.
Attachments
Issue Links
- is related to
-
KAFKA-16290 Investigate propagating subscription state updates via queues
- Open