tursodatabase / tursodatabase/libsql
Bottomless replication requires synchronous call to S3
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
The issue applies both to namespace loading and metastore loading during startup.
This causes cold start to take over 10s in some cases since it requires multiple roundtrips to S3.
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 tracing startup through namespace loading and metastore loading, focusing on the synchronous S3 calls and their multiple roundtrips. The issue mentions no files or tests, so locate the relevant startup entry points first. Done means bottomless replication no longer requires synchronous S3 calls that make cold starts exceed 10 seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, c
- Domain
- cloud, databases, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100