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 2023/02/02 19:17:00 UTC
[jira] [Comment Edited] (KAFKA-12639) AbstractCoordinator ignores backoff timeout when joining the consumer group
[ https://issues.apache.org/jira/browse/KAFKA-12639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683545#comment-17683545 ]
Philip Nee edited comment on KAFKA-12639 at 2/2/23 7:16 PM:
------------------------------------------------------------
Hey [~matiss.gutmanis] - I'm arriving at the same conclusion as what Guozhang previous mentioned, would you mind sharing/briefly describe your test environment?
[~guozhang] - should we could exit upon expired timer? maybe something like
```
if (timer.isExpired())
{ return false; }
timer.sleep(rebalanceConfig.retryBackoffMs);
```
was (Author: JIRAUSER283568):
Hey [~matiss.gutmanis] - I'm arriving at the same conclusion as what Guozhang previous mentioned, would you mind sharing/briefly describe your test environment?
[~guozhang] - should we exit upon expired timer?
```
if (timer.isExpired()) {
return false;
}
timer.sleep(rebalanceConfig.retryBackoffMs);
```
> AbstractCoordinator ignores backoff timeout when joining the consumer group
> ---------------------------------------------------------------------------
>
> Key: KAFKA-12639
> URL: https://issues.apache.org/jira/browse/KAFKA-12639
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 2.7.0
> Reporter: Matiss Gutmanis
> Assignee: Philip Nee
> Priority: Major
>
> We observed heavy logging while trying to join consumer group during partial unavailability of Kafka cluster (it's part of our testing process). Seems that {{rebalanceConfig.retryBackoffMs}} used in {{ org.apache.kafka.clients.consumer.internals.AbstractCoordinator#joinGroupIfNeeded}} is not respected. Debugging revealed that {{Timer}} instance technically is expired thus using sleep of 0 milliseconds which defeats the purpose of backoff timeout.
> Minimal backoff timeout should be respected.
>
> {code:java}
> 2021-03-30 08:30:24,488 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] JoinGroup failed: Coordinator 127.0.0.1:9092 (id: 2147483634 rack: null) is loading the group.
> 2021-03-30 08:30:24,488 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] Rebalance failed.
> org.apache.kafka.common.errors.CoordinatorLoadInProgressException: The coordinator is loading and hence can't process requests.
> 2021-03-30 08:30:24,488 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] (Re-)joining group
> 2021-03-30 08:30:24,489 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] JoinGroup failed: Coordinator 127.0.0.1:9092 (id: 2147483634 rack: null) is loading the group.
> 2021-03-30 08:30:24,489 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] Rebalance failed.
> org.apache.kafka.common.errors.CoordinatorLoadInProgressException: The coordinator is loading and hence can't process requests.
> 2021-03-30 08:30:24,489 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] (Re-)joining group
> 2021-03-30 08:30:24,490 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] JoinGroup failed: Coordinator 127.0.0.1:9092 (id: 2147483634 rack: null) is loading the group.
> 2021-03-30 08:30:24,490 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] Rebalance failed.
> org.apache.kafka.common.errors.CoordinatorLoadInProgressException: The coordinator is loading and hence can't process requests.
> 2021-03-30 08:30:24,490 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] (Re-)joining group
> 2021-03-30 08:30:24,491 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] JoinGroup failed: Coordinator 127.0.0.1:9092 (id: 2147483634 rack: null) is loading the group.
> 2021-03-30 08:30:24,491 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] Rebalance failed.
> org.apache.kafka.common.errors.CoordinatorLoadInProgressException: The coordinator is loading and hence can't process requests.
> 2021-03-30 08:30:24,491 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] (Re-)joining group
> 2021-03-30 08:30:24,492 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] JoinGroup failed: Coordinator 127.0.0.1:9092 (id: 2147483634 rack: null) is loading the group.
> 2021-03-30 08:30:24,492 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] Rebalance failed.
> org.apache.kafka.common.errors.CoordinatorLoadInProgressException: The coordinator is loading and hence can't process requests.
> 2021-03-30 08:30:24,492 INFO [fs2-kafka-consumer-41][o.a.k.c.c.i.AbstractCoordinator] [Consumer clientId=app_clientid, groupId=consumer-group] (Re-)joining group
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)