Kafka: Continuously getting FETCH_SESSION_ID_NOT_FOUND

Question

I am continuously getting FETCH_SESSION_ID_NOT_FOUND. I\'m not sure why its happening. Can anyone please me here what is the problem and what will be the impact on consumers

Answer 1

This is not an error, it's INFO and it's telling you that you are connected but it can't fetch a session id because there's none to fetch.

It's normal to see this message and the flushing message in the log.

Answer 2

I have increased it at first from 1K to 2K, and in the second step from 2K to 4K, and as long as the limit was not exhausted, there was no appearance of error:

As it seemed to me like a session leak by certain unidentified consumer, I didn't try 10K limit yet, but reading Hrishikesh Mishra's answer, I definitely will. Because, increasing the limit also decreased the frequency of error, so the question of identifying individual consumer groups that are opening excessive number of incremental fetch sessions, mentioned here How to check the actual number of incremental fetch session cache slots used in Kafka cluster? , may be irrelevant in the end.

Answer 3

Increase the value of max.incremental.fetch.session.cache.slots. The default value is 1K, in my case I have increased it to 10K and it fixed.