🔒 Paid
Read Replica Lag
A write-heavy batch job on your primary database has pushed replication to your read replica into a growing backlog. Reads served from the replica are returning stale data, a reporting job is about to make it worse, and consumers that depend on strong consistency are starting to see incorrect results. Diagnose the lag and restore read consistency before it spreads further.
- Difficulty
- Senior
- Expected Time
- ~14 min
- Category
- Databases & Storage
Skills
- Diagnosing replication lag and stale reads
- Read-your-writes routing strategies
- Consistency vs. read-scaling tradeoffs
- Recognizing plausible-but-harmful mitigations
System Architecture
- Write Service
- Primary Database
- Read Replica
- Read Service
- Reporting Job
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents