[jira] [Commented] (KAFKA-15531) Ensure coordinator node is removed upon disconnection exception

["Philip Nee (Jira)" <ji...@apache.org>]

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

Philip Nee commented on KAFKA-15531:
------------------------------------

this was fixed here: [https://github.com/apache/kafka/pull/14639/files]

 

 

> Ensure coordinator node is removed upon disconnection exception
> ---------------------------------------------------------------
>
>                 Key: KAFKA-15531
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15531
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, consumer
>            Reporter: Philip Nee
>            Assignee: Philip Nee
>            Priority: Major
>              Labels: kip-848, kip-848-client-support, kip-848-e2e, kip-848-preview
>
> In the async consumer, the coordinator isn't being removed when receiving the following exception:
>  
> {code:java}
> (e instanceof DisconnectException) {
>   markCoordinatorUnknown(true, e.getMessage());
> }{code}
>  
> This should happen on all requests going to coordinator node:
> 1. heartbeat 2. offset fetch/commit 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)