redpanda-data / redpanda-data/console
Suggestion: Kafka Could not describe cluster
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
We use console 2.1.1 version and when console tries to connect broker and get the list it fails.
/api/cluster is the endpoint
{statusCode: 500, message: "Could not describe cluster"}
message
:
"Could not describe cluster"
statusCode
:
500
because there is hardcoded 6sec https://github.com/redpanda-data/console/blob/master/backend/pkg/console/brokers.go#L74. could you please parameterize this? so that we can configure the custom value ?
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 with backend/pkg/console/brokers.go at line 74 and trace how the /api/cluster endpoint describes the Kafka cluster. Parameterize the hardcoded six-second timeout so users can configure a custom value; done means the endpoint uses that configured timeout instead of the fixed value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100