tursodatabase / tursodatabase/libsql
if the machine is stopped during snapshot, can result in data loss
Open
Nobody has claimed this yet.
bottomless
nemesis
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
To reproduce:
- Create a large DB
- When the snapshot upload is in progress to S3, kill the machine or libsql-server process
- Wipe the volume and restore from S3
- The restoration does not complain (#718) and when I checked in shell, it shows the data to be empty
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 reproducing the failure during the S3 snapshot upload, then inspect the libsql-server snapshot and restoration paths involved after the process is killed. Verify that an interrupted snapshot cannot restore as an apparently empty database and that restoration reports the failure instead of silently succeeding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100