Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-16160

AsyncKafkaConsumer is trying to connect to a disconnected node in a tight loop

    XMLWordPrintableJSON

Details

    Description

      Observing some excessive logging running AsyncKafkaConsumer and observing excessive logging of :

      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)

      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 should be a blocker for 3.8 release.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. KAFKA-15250 ConsumerNetworkThread is running tight loop

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              phuctran Phuc Hong Tran
              pnee Philip Nee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: