[
https://issues.apache.org/jira/browse/KAFKA-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802158#comment-17802158
]
Phuc Hong Tran commented on KAFKA-15867:
----------------------------------------
[~pnee] I happened to come across this comment:
[https://github.com/apache/kafka/blob/60c445bdd51c608d1212f5cab83b65533739bd61/clients/src/main/java/org/apache/kafka/clients/consumer/internals/events/ApplicationEventProcessor.java#L61]
[~kirktrue], may you give some insights on why we don't want to propagate the
error to the caller? Thanks
> 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
> 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)
