redpanda-data / redpanda-data/console
Improve performance of consumer-group routes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
I have a large cluster of ~45k consumer groups. Opening the Consumer Group tab in the frontend times out in the 25 second default that fetch waits for responses from the backend. I can see in debug logs that the operation takes about 5 minutes to complete the request to GET /api/consumer-groups for my cluster.
Contributor guide
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 tracing the Consumer Group tab to the GET /api/consumer-groups entry point and compare the frontend fetch timeout with the reported five-minute request on a large cluster. The work is done when the consumer-group view can load a cluster of roughly 45k groups without timing out; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, react, typescript
- Domain
- api, frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100