cockroachdb / cockroachdb/cockroach
ui: do not retry table metadata polling requests when a 5xx is returned
Open
C-bug
T-observability
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
We should add a rate limit for the retries to the `api/v2/table_metadata/updatejob/?onlyIfStale=true"` call and use exponential decay. Current behavior will spam the cluster and frontend logs when a rolling restart is happening
Jira issue: CRDB-50499
Contributor guide
Assessment
This issue has not been assessed yet.