[ https://issues.apache.org/jira/browse/KAFKA-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirk True updated KAFKA-15867: ------------------------------ Labels: consumer-threading-refactor events (was: consumer-threading-refactor) > Should ConsumerNetworkThread wrap the exception and notify the polling thread? > ------------------------------------------------------------------------------ > > Key: KAFKA-15867 > URL: https://issues.apache.org/jira/browse/KAFKA-15867 > Project: Kafka > Issue Type: Task > Components: clients, consumer > Reporter: Philip Nee > Assignee: Phuc Hong Tran > Priority: Minor > Labels: consumer-threading-refactor, events > Fix For: 3.8.0 > > > The ConsumerNetworkThread runs a tight loop infinitely. However, when > encountering an unexpected exception, it logs an error and continues. > > I think this might not be ideal because user can run blind for a long time > before discovering there's something wrong with the code; so I believe we > should propagate the throwable back to the polling thread. > > cc [~lucasbru] -- This message was sent by Atlassian Jira (v8.20.10#820010)