You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2024/12/09 20:44:00 UTC

[jira] [Updated] (KAFKA-18189) CoordinatorRequestManager log message can include incorrect coordinator disconnect time

     [ https://issues.apache.org/jira/browse/KAFKA-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk True updated KAFKA-18189:
------------------------------
    Summary: CoordinatorRequestManager log message can include incorrect coordinator disconnect time  (was: CoordinatorRequestManager log of time disconnected from coordinator is incorrect)

> CoordinatorRequestManager log message can include incorrect coordinator disconnect time
> ---------------------------------------------------------------------------------------
>
>                 Key: KAFKA-18189
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18189
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>    Affects Versions: 3.9.0
>            Reporter: Kirk True
>            Assignee: Kirk True
>            Priority: Minor
>              Labels: consumer-threading-refactor
>             Fix For: 4.0.0
>
>
> The {{CoordinatorRequestManager}} outputs some logging when the client is not able to connect with the coordinator for an extended period of time:
> {quote}Consumer has been disconnected from the group coordinator for Xms
> {quote}
>  
> However, if the coordinator is marked as _unknown_ before it was ever {_}known{_}, the calculation used to determine that is incorrect which sometimes leads to logs like:
>  
> {quote}Consumer has been disconnected from the group coordinator for 1733769862524ms
> {quote}
>  
>  



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