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/01/19 20:37:00 UTC
[jira] [Commented] (KAFKA-16178) AsyncKafkaConsumer doesn't retry joining the group after rediscovering group coordinator
[ https://issues.apache.org/jira/browse/KAFKA-16178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808801#comment-17808801 ]
Philip Nee commented on KAFKA-16178:
------------------------------------
Seems to be an issue with the RequestState - I wonder if we've forgotten to update the lastReceivedMs when receiving these errors.
> AsyncKafkaConsumer doesn't retry joining the group after rediscovering group coordinator
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-16178
> URL: https://issues.apache.org/jira/browse/KAFKA-16178
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: Dongnuo Lyu
> Priority: Critical
> Labels: consumer-threading-refactor
> Attachments: pkc-devc63jwnj_jan19_0_debug
>
>
> {code:java}
> [2024-01-17 21:34:59,500] INFO [Consumer clientId=consumer.7e26597f-0285-4e13-88d6-31500a500275-0, groupId=consumer-groups-test-0] Discovered group coordinator Coordinator(key='consumer-groups-test-0', nodeId=3, host='b3-pkc-devc63jwnj.us-west-2.aws.devel.cpdev.cloud', port=9092, errorCode=0, errorMessage='') (org.apache.kafka.clients.consumer.internals.CoordinatorRequestManager:162)
> [2024-01-17 21:34:59,681] INFO [Consumer clientId=consumer.7e26597f-0285-4e13-88d6-31500a500275-0, groupId=consumer-groups-test-0] GroupHeartbeatRequest failed because the group coordinator Optional[b3-pkc-devc63jwnj.us-west-2.aws.devel.cpdev.cloud:9092 (id: 2147483644 rack: null)] is incorrect. Will attempt to find the coordinator again and retry in 0ms: This is not the correct coordinator. (org.apache.kafka.clients.consumer.internals.HeartbeatRequestManager:407)
> [2024-01-17 21:34:59,681] INFO [Consumer clientId=consumer.7e26597f-0285-4e13-88d6-31500a500275-0, groupId=consumer-groups-test-0] Group coordinator b3-pkc-devc63jwnj.us-west-2.aws.devel.cpdev.cloud:9092 (id: 2147483644 rack: null) is unavailable or invalid due to cause: This is not the correct coordinator.. Rediscovery will be attempted. (org.apache.kafka.clients.consumer.internals.CoordinatorRequestManager:136)
> [2024-01-17 21:34:59,882] INFO [Consumer clientId=consumer.7e26597f-0285-4e13-88d6-31500a500275-0, groupId=consumer-groups-test-0] Discovered group coordinator Coordinator(key='consumer-groups-test-0', nodeId=3, host='b3-pkc-devc63jwnj.us-west-2.aws.devel.cpdev.cloud', port=9092, errorCode=0, errorMessage='') (org.apache.kafka.clients.consumer.internals.CoordinatorRequestManager:162){code}
> Some of the consumers don't consume any message. The logs show that after the consumer starts up and successfully logs in,
> # The consumer discovers the group coordinator.
> # The heartbeat to join group fails because "This is not the correct coordinator"
> # The consumer rediscover the group coordinator.
> Another heartbeat should follow the rediscovery of the group coordinator, but there's no logs showing sign of a heartbeat request.
> On the server side, there is completely no log about the group id. A suspicion is that the consumer doesn't send a heartbeat request after rediscover the group coordinator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)