cockroachdb / cockroachdb/pebble
Backup/DR: default to fewer full backups on cold-tier clusters
Closed
A-storage
F-tiered-storage
T-storage
- Dominant language
- Go
- Stars
- 6k
- Forks
- 584
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 5
Description
Integrate backup job with rate limiter; enforce incremental-first strategy (e.g., weekly full) to respect cold-tier bandwidth constraints; provide guardrails.
Jira issue: PEBBLE-1273
Epic CRDB-48982
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the backup job and rate-limiter integration in the Go code, then trace how full and incremental backups are selected for cold-tier clusters. Done means cold-tier bandwidth is respected through an incremental-first policy, with guardrails and fewer full backups by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100