You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2024/08/29 17:30:00 UTC

[jira] [Commented] (KAFKA-15867) Should ConsumerNetworkThread wrap the exception and notify the polling thread?

    [ https://issues.apache.org/jira/browse/KAFKA-15867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877811#comment-17877811 ] 

Colin McCabe commented on KAFKA-15867:
--------------------------------------

Changing target fix version to 4.0 since this is not a blocker and we are past code freeze

> 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.9.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)