cockroachdb / cockroachdb/cockroach
observability: capture high memory usage/long running queries
Open
A-cluster-observability
C-enhancement
T-observability
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
### Problem:
Currently if an Out Of Memory exception is hit there is no observability into which query cause the OOM. The current logging and stats recording is done on query completion.
### Solution options:
1. Add a log that captures long running queries with high memory usage.
2. Add info to the stats collection to flush info about long running queries before query is completed.
3. Add memory usage to insights detection
Jira issue: CRDB-27989
Epic CRDB-32139
Contributor guide
Assessment
This issue has not been assessed yet.