Skip to content
All concepts

Concept

Replication lag

Replication lag is the delay between a change being confirmed on the primary database and that change appearing on a replica. During the delay the replica answers with slightly old data. It is normally milliseconds and grows under heavy writes, long transactions or a slow network.

Watch a user save a change and reload: the replica has not received it yet, so the change seems to be missing. A live step from the lesson Replication lag (Consensus & replication). Timings and counts are illustrative.

Where you'll see it