Skip to content

fix(backend): make operation timeouts configurable#2412

Open
grassiale wants to merge 1 commit intoredpanda-data:masterfrom
grassiale:configurable-operation-timeouts
Open

fix(backend): make operation timeouts configurable#2412
grassiale wants to merge 1 commit intoredpanda-data:masterfrom
grassiale:configurable-operation-timeouts

Conversation

@grassiale
Copy link
Copy Markdown

@grassiale grassiale commented Apr 22, 2026

Fixes #2410

On large clusters (e.g. AWS MSK with thousands of partitions and IAM authentication), the hardcoded 6s timeout in GetClusterInfo and 5s timeout in GetTopicsOverview lead to errors such as "context deadline exceeded" and broken broker connections.

This patch introduces a new OperationTimeouts config block under console.operationTimeouts with clusterInfo and topicsOverview duration fields. The original values (6s / 5s) are default.

Example configuration:

  console:
    operationTimeouts:
      clusterInfo: 30s
      topicsOverview: 30s

I'm not sure if the configuration should be under console or under kafka

@grassiale grassiale changed the title config/console: make operation timeouts configurable fix(backend): make operation timeouts configurable Apr 22, 2026
@grassiale grassiale force-pushed the configurable-operation-timeouts branch from e494243 to c99551f Compare April 22, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hardcoded context timeouts in GetClusterInfo/GetTopicsOverview cause failures on large clusters

1 participant