Re: Kafka attempt rediscovery never happen

Hi Antonio,
What you can do is to check the broker side log, to see if there's any
info. If no, you can also enable DEBUG log to have more info for
troubleshooting.

Thank you.
Luke

On Mon, Aug 23, 2021 at 11:27 PM Antonio Pires <smborgespires@gmail.com>
wrote:

> Hello fellow Kafka users,
>
> I've been trying to understand what happened to one of my Consumers but
> with no luck so far, but maybe someone could help me with some insight.
>
> I got these lines on the logs
>
> │ 20:43:43,909 INFO com.mms.logic [] -
> Successfully consumed message.
> correlationId=ce62d95e-09e4-4f8f-b166-5193d582733b topic=nj_topic
> partition=2 offset=371360
> │ 20:43:55,281 ERROR
> org.apache.kafka.clients.consumer.internals.ConsumerCoordinator [] -
> [Consumer clientId=consumer-mms-1, groupId=mms] Offset commit failed on
> partition nj_topic-2 at offset 371361: The coordinator is not aware of this
> member.
> │ 20:43:55,282 INFO
> org.apache.kafka.clients.consumer.internals.ConsumerCoordinator [] -
> [Consumer clientId=consumer-mms-1, groupId=mms] OffsetCommit failed with
> Generation{generationId=17,
> memberId='consumer-mms-1-c69e919b-2719-42cf-bf76-687fb1b0ea18',
> protocol='range'}: The coordinator is not aware of this member.
> │ 20:43:55,281 INFO
> org.apache.kafka.clients.consumer.internals.AbstractCoordinator [] -
> [Consumer clientId=consumer-mms-1, groupId=mms] Group coordinator
> njss1.env.net:9092 (id: 2147483646 rack: null) is unavailable or invalid,
> will attempt rediscovery
>
> After this nothing else is logged, no actual attempt to rediscover the
> coordinator and rejoin is made but I still get a response from the webping
> endpoint of the service which is running the consumer, meaning the service
> did not go down but the consumer for some reason did not retry to commit
> the offset.
>
> Any ideas?
>
> Regards
> Antonio
>