You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2026/04/17 16:29:00 UTC

[jira] [Updated] (KAFKA-20426) Using both group.id and assign() causes a busy loop in AsyncKafkaConsumer

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

Lianet Magrans updated KAFKA-20426:
-----------------------------------
    Component/s: clients

> Using both group.id and assign() causes a busy loop in AsyncKafkaConsumer
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-20426
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20426
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>            Reporter: Chia-Ping Tsai
>            Assignee: Kuan Po Tseng
>            Priority: Critical
>
> When using AsyncKafkaConsumer with a configured group.id, but relying on manual assignment (consumer.assign()) instead of subscribe(), the pollForFetches will return quickly and result in a busy loop.
> The root cause is that the method AbstractHeartbeatRequestManager#maximumTimeToWait always returns 0 since heartbeatTimer is not updated when it is in the UNSUBSCRIBED state.



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