Lag in context
Do not read lag alone. Compare it with heartbeat age, source workload, rows applied, and recent CDC errors.
MySQL Replication Lag
Know when MySQL replication is caught up enough to trust.
Lag only matters when teams can act on it. Cupcake DRCP keeps replication lag tied to stream health, heartbeat freshness, workload activity, compare status, and cutover readiness.
Why It Matters
Turn database movement into an operating workflow.
Cutover confidence
Use lag plus compare results to decide whether a target is ready to promote.
Recovery drills
Keep a record of stream state so failover and recovery tests have evidence, not anecdotes.
Product Workflows
Related Cupcake DRCP screens.
Checklist
Replication lag recovery readiness checklist
Step 1
Confirm the source is still producing heartbeats and the target worker is still polling.
Step 2
Compare lag with recent rows applied so a quiet system is not mistaken for a stalled system.
Step 3
Review the last CDC error and the current source position before promoting a target.
Step 4
Run compare on cutover-critical tables when lag returns inside the acceptable window.
Community Discovery
Useful MySQL operations topics to keep exploring.
FAQs
Quick answers.
Is zero lag required?
Not always. The right threshold depends on the migration or recovery objective, but teams need a clear signal before cutover.
How does Cupcake help when lag grows?
It highlights heartbeat state, polling state, source load, and technical CDC events so operators can investigate quickly.