Document / automate creating lightweight snapshot on the same filesystem for durablilty
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
Is your feature request related to a problem?
There are users who want to run QuestDB on unstable hardware where power can be randomly reset. That can be
industrial uses where the DB runs on Raspberry Pi or similar on equipment or machinery
Windows users who run the DB at home can suffer from random software updates and domestic power issues. Sometimes these users are OK to sacrifice a small portion of their data like 1 hour or 15 mins in the even of hard power reset but keep running the DB in async mode.
Describe the solution you'd like.
Document or automate the creation of lightweight checkpoints on the same file system using hard links so that users can implement this mechanism.
Describe alternatives you've considered.
No response
Full Name:
Alex Pelagenko
Affiliation:
QuestDB
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading related issue #4829 and the existing QuestDB durability and storage documentation. Determine whether the requested same-filesystem hard-link checkpoint should be documented or automated, and define completion as a usable procedure or workflow that preserves the stated bounded data-loss tradeoff after a hard reset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100