tursodatabase / tursodatabase/libsql
Mechanism for probing if a replica is up-to-date?
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Multiple people have been asking if there's a way to probe if a replica is up-to-date wrt. primary. In LiteFS, for example, replicas know a "transaction ID" that you can use to do this check. Let's figure out the use case for this and expose something similar in libSQL.
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 files, tests, or entry points are named. Start by clarifying the use case for checking replica freshness and compare the proposed transaction-ID approach with LiteFS; done should mean a specified, exposed mechanism for determining whether a replica is up to date with its primary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100