tursodatabase / tursodatabase/libsql
Replication lag metrics
Open
Nobody has claimed this yet.
enhancement
good first issue
help wanted
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Let's add metrics to measure replication lag so that you can observe it. For example, let's assume that the clocks are synchronized and take a timestamp when we stream out a page frame and compare that to the timestamp when we inject the frame to the replica WAL.
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 the replication path between streaming out a page frame and injecting it into the replica WAL. Check how timestamps and metrics are currently handled, then define completion as exposing a replication-lag measurement based on those two timestamps and validating it in the relevant replication tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust, sqlite
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100