cockroachdb / cockroachdb/cockroach
Indicate whether a client-side or server-side retry was due to the closed timestamp interval
Open
C-enhancement
T-observability
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
We should surface observability into whether a transaction and statement retried due to hitting the closed timestamp threshold.
Few experiences to update:
- For a failed 40001 insight, indicate (boolean) the push reason
- Statement and transaction statistics, indicate number of times threshold was hit
Related issue from KV: https://github.com/cockroachdb/cockroach/issues/93954
Jira issue: CRDB-24140
Contributor guide
Assessment
This issue has not been assessed yet.