tursodatabase / tursodatabase/libsql
Replication log recovery blocks namespace loading
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
This can be a problem for big databases, where the log recovery can take hours and saturate CPU from the box.
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
No file, test, or entry point is named; begin by locating the replication log recovery and namespace-loading paths in the repository. Clarify the intended behavior for large databases, then define completion criteria around whether namespace loading can proceed during recovery and how recovery resource use should be evaluated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100