Logstash Kafka client logs many INVALID_FETCH_SESSION_EPOCH messages

In our production environment (elastic 7.3) we have a lot of logs from Logstash with the following messages:

[Consumer clientId=metrics_prod-0, groupId=internal_in_metrics_prod] Node 3 was unable to process the fetch request with (sessionId=1631518421, epoch=5480): INVALID_FETCH_SESSION_EPOCH.

it's the logstash.log.module: org.apache.kafka.clients.FetchSessionHandler that logs the message as an INFO

When googling this it seems that this issue could be related to the Kafka client issue reported on https://issues.apache.org/jira/browse/KAFKA-8052

For Kafka client 2.1.0 (which logstash uses) this seems to be an issue. The issue was solved in Kafka client 2.3.0.

Any plans on upgrading to Kafka 2.3.0+ for logstash so this issue can be resolved?

It looks like the client was updated about a week ago (https://github.com/logstash-plugins/logstash-integration-kafka/commit/5e7e4d6366fed708e4270ce57ba8210f9743e3dc). It will probably be in the next release of the plugin.


GitHub YouTube LinkedIn
How to install Elasticsearch & Kibana on Ubuntu - incl. hardware recommendations
What is the best storage technology for Elasticsearch?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.