Philip Nee created KAFKA-16160: ---------------------------------- Summary: AsyncKafkaConsumer is trying to connect to a disconnected note in a tight loop Key: KAFKA-16160 URL: https://issues.apache.org/jira/browse/KAFKA-16160 Project: Kafka Issue Type: Task Components: consumer Reporter: Philip Nee
Observing some excessive logging running AsyncKafkaConsumer and observing excessive logging of : {code:java} 1271 [2024-01-15 09:43:36,627] DEBUG [Consumer clientId=console-consumer, groupId=concurrent_consumer] Node is not ready, handle the request in the next event loop: node=worker4:9092 (id: 2147483644 rack: null), request=UnsentRequest{requestBuil der=ConsumerGroupHeartbeatRequestData(groupId='concurrent_consumer', memberId='laIqS789StuhXFpTwjh6hA', memberEpoch=1, instanceId=null, rackId=null, rebalanceTimeoutMs=300000, subscribedTopicNames=[output-topic], serverAssignor=null, topicP artitions=[TopicPartitions(topicId=I5P5lIXvR1Cjc8hfoJg5bg, partitions=[0])]), handler=org.apache.kafka.clients.consumer.internals.NetworkClientDelegate$FutureCompletionHandler@918925b, node=Optional[worker4:9092 (id: 2147483644 rack: null)] , timer=org.apache.kafka.common.utils.Timer@55ed4733} (org.apache.kafka.clients.consumer.internals.NetworkClientDelegate) {code} This seems to be triggered by a tight poll loop of the network thread. The right thing to do is to backoff a bit for that given node and retry later. -- This message was sent by Atlassian Jira (v8.20.10#820010)