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

Posted to jira@kafka.apache.org by "Viktor Somogyi-Vass (Jira)" <ji...@apache.org> on 2022/05/19 13:37:00 UTC

[jira] [Created] (KAFKA-13917) Avoid calling lookupCoordinator() in tight loop

Viktor Somogyi-Vass created KAFKA-13917:
-------------------------------------------

             Summary: Avoid calling lookupCoordinator() in tight loop
                 Key: KAFKA-13917
                 URL: https://issues.apache.org/jira/browse/KAFKA-13917
             Project: Kafka
          Issue Type: Improvement
          Components: consumer
    Affects Versions: 3.1.1, 3.1.0, 3.1.2
            Reporter: Viktor Somogyi-Vass
            Assignee: Viktor Somogyi-Vass


Currently the heartbeat thread's lookupCoordinator() is called in a tight loop if brokers crash and the consumer is left running. Besides that it floods the logs on debug level, it increases CPU usage as well.

The fix is easy, just need to put a backoff call after coordinator lookup.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)