cockroachdb / cockroachdb/cockroach
kv: improve observability into under-replicated ranges
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
_Adapted from CRDB-40230._
Currently, our logs will only indicate there are under-replicated ranges, but they don't say _why_ these ranges are under-replicated.
The _why_ requires knowledge and analysis of log files (or files in a debug.zip). These are often difficult to parse.
Improve our logging and how we display and report on under-replicated ranges in the DB console.
Jira issue: CRDB-41374
Contributor guide
Research direction
Start by reviewing the existing logging and DB console reporting for under-replicated ranges. Determine how the current system identifies these ranges and what information is needed to explain why they are under-replicated; done means the cause is surfaced in logs and displayed in the DB console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100