Consumer could not connect Kafka

[barryzhounb]

It is very often to happen that my consumer could not connect Kafka cluster, and I saw the following warnings.

I am wondering what happens and how to fix it?

2021-07-16 14:12:19,837 [KafkaMessageReceiver] org.apache.kafka.clients.consumer.internals.ConsumerCoordinator: [ERROR] [Consumer clientId=dlcConsumer1, groupId=atest-group-management-cp4s-to-dlc] Offset commit failed on partition atest-management-cp4s-to-dlc-topic-0 at offset 0: The coordinator is not aware of this member.
2021-07-16 14:12:19,838 [KafkaMessageReceiver] org.apache.kafka.clients.consumer.internals.ConsumerCoordinator: [WARN] [Consumer clientId=dlcConsumer1, groupId=atest-group-management-cp4s-to-dlc] Asynchronous auto-commit of offsets {atest-management-cp4s-to-dlc-topic-0=OffsetAndMetadata{offset=0, leaderEpoch=null, metadata=''}, atest-management-cp4s-to-dlc-topic-3=OffsetAndMetadata{offset=0, leaderEpoch=null, metadata=''}, atest-management-cp4s-to-dlc-topic-5=OffsetAndMetadata{offset=0, leaderEpoch=null, metadata=''}} failed: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.

2021-07-16 14:12:19,839 [KafkaMessageReceiver] org.apache.kafka.clients.consumer.internals.ConsumerCoordinator: [WARN] [Consumer clientId=dlcConsumer1, groupId=atest-group-management-cp4s-to-dlc] Synchronous auto-commit of offsets {atest-management-cp4s-to-dlc-topic-1=OffsetAndMetadata{offset=3, leaderEpoch=0, metadata=''}, atest-management-cp4s-to-dlc-topic-0=OffsetAndMetadata{offset=0, leaderEpoch=null, metadata=''}, atest-management-cp4s-to-dlc-topic-3=OffsetAndMetadata{offset=0, leaderEpoch=null, metadata=''}, atest-management-cp4s-to-dlc-topic-2=OffsetAndMetadata{offset=4, leaderEpoch=0, metadata=''}, atest-management-cp4s-to-dlc-topic-5=OffsetAndMetadata{offset=0, leaderEpoch=null, metadata=''}, atest-management-cp4s-to-dlc-topic-4=OffsetAndMetadata{offset=1, leaderEpoch=0, metadata=''}} failed: Offset commit cannot be completed since the consumer is not part of an active group for auto partition assignment; it is likely that the consumer was kicked out of the group.

[tomncooper]

As it says in the error message: The commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records.