Burrow floods FetchSessionCache on Kafka Broker

[vas78]

When running Burrow 1.3.2 with Kafka client version 2.1.0 (or higher) against a Kafka 2.1.1 cluster, the FetchSessionCache on Kafka Broker gets flooded with new entries which eventually leads to FetchSessionCache evictions. In the screenshot below Burrow 1.3.2 had been started at around 16:37, Broker FetchSessionCache is limited to 5000:

The workaround is either downgrading to Kafka client 2.0.1 (or lower) or downgrading Burrow to 1.2.2 which works perfectly fine with Kafka client 2.1.0 in this case. So it may be either Burrow or Sarama issue.

[giladam]

We recently upgraded from Burrow 1.2.2 with Kafka Client 2.1.0 to Burrow 1.3.3 with Kafka Client 2.4.0 and following this upgrade we saw increased reports of "FETCH_SESSION_ID_NOT_FOUND" errors so we downgraded back to Burrow 1.2.2 as a precautionary measure after seeing this issue.

Currently, we have not increased our fetch session cache size on our brokers but we plan to.

So perhaps we are seeing this issue as well. (or it could be a coincidence)

[ninjasftw]

I just got bit by the same issue. rebuilt Burrow using a later version of sarama to support Kafka 2.4 and it seems to be ok for the moment.

[alvarobacelar]

@vas78 , You updated the Burrow for this version v1.3.4?