redpanda-data / redpanda-data/console
Hardcoded context timeouts in ListMessages cause failures
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
Description:
When Apache Kafka read/write throughput is slow, consuming messages based on a specific timestamp can exceed the default timeout (35s), leading to failures.
Expected Behavior
Make the timeout configurable instead of hardcoded.
Environment
console version: v3.5.2 / 3.6.0 / 3.7.2
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 in backend/pkg/api/connect/service/console/service.go at the linked ListMessages implementation and inspect how its context timeout is currently set. Trace the timeout through the message-consumption path and identify the configuration boundary it should use. Done means slow timestamp-based Kafka reads no longer fail because of a fixed 35-second limit, with the timeout configurable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100