[ https://issues.apache.org/jira/browse/KAFKA-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson resolved KAFKA-7764. ------------------------------------ Resolution: Fixed This was fixed by the patch for KAFKA-7831 which removes the metadata listener. > Authentication exceptions during consumer metadata updates may not get > propagated > --------------------------------------------------------------------------------- > > Key: KAFKA-7764 > URL: https://issues.apache.org/jira/browse/KAFKA-7764 > Project: Kafka > Issue Type: Bug > Components: consumer > Reporter: Jason Gustafson > Assignee: Dhruvil Shah > Priority: Major > > The consumer should propagate authentication errors to the user. We handle > the common case in ConsumerNetworkClient when the exception occurs in > response to an explicitly provided request. However, we are missing the logic > to propagate exceptions during metadata updates, which are handled internally > by NetworkClient. This logic exists in > ConsumerNetworkClient.awaitMetadataUpdate, but metadata updates can occur > outside of this path. Probably we just need to move that logic into > ConsumerNetworkClient.poll() so that errors are always checked. -- This message was sent by Atlassian JIRA (v7.6.3#76005)