Burrow floods FetchSessionCache on Kafka Broker
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with Burrow 1.3.2, Kafka client 2.1.0 or higher, and a Kafka 2.1.1 cluster, then compare it with Burrow 1.2.2 and client 2.0.1. Investigate whether the regression is in Burrow or Sarama and verify completion by preventing FetchSessionCache flooding and evictions under the reported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100