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

[jira] [Commented] (KAFKA-16819) CoordinatorRequestManager seems to return 0ms during the coordinator discovery

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

Philip Nee commented on KAFKA-16819:
------------------------------------

This was resolved via request state fixed.

> CoordinatorRequestManager seems to return 0ms during the coordinator discovery
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-16819
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16819
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>            Reporter: Philip Nee
>            Assignee: Philip Nee
>            Priority: Minor
>              Labels: consumer-threading-refactor
>             Fix For: 3.9.0
>
>
> In KAFKA-15250 we discovered the ConsumerNetworkThread is looping without much backoff.  The in-flight check PR fixed a lot of it; however, during the coordinator discovery phase, CoordinatorRequestManager would keep on returning 0 before the coordinator node was found.
>  
> The impact is minor but we should be expecting the coordinator manager to backoff until the exp backoff expired (so it should return around 100ms).



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