cockroachdb / cockroachdb/pebble
db: delay deletion of WALs at Open
- Dominant language
- Go
- Stars
- 6k
- Forks
- 584
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 5
Description
During Open we replay old WALs and promptly delete them. This limits our ability to debug issues with corruption at the tail of the WAL. We could consider delaying the deletion of existing WALs (or files in general) until some fixed time after the database has opened.
Linking to cockroachlabs/support#2369.
Jira issue: PEBBLE-43
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names the Open path and WAL replay/deletion behavior but no files or tests. Start by tracing how Open replays and deletes existing WALs, then clarify the retention timing and what corruption-debugging behavior counts as done before implementing and validating the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100