Skip to main content

Replication latency

Reducing lag between replicated target data and source operations

Abstract

File and tablKnowing your current replication state is critical information. Replicated target data can occasionally fall behind source operations.

Knowing your current replication state is critical information. Replicated target data can occasionally fall behind source operations. While replication will eventually bring the two nodes into full consistency, it is useful to know the degree to which replication remains behind.

Latency is used to measure this state. A latency value is the time difference between the target commit time from the original source node commit time.

Figure 1. Replication Latencies Tab
Replication Latencies Tab


Replication latencies options:
  • Latency Warnings (secs)

    Latency warnings output when latency times exceed threshold values (in seconds).

  • Latency Error (secs)

    Latency errors are output when latency times exceed threshold values (in seconds).

  • Disable Latency Check

    Latency checking can be disabled if desired meaning no warnings are errors are reported.

Notifications

Warnings and errors are displayed visually in the browser view for that plan. Current latency values are reported n the Latency column in the Plan activity for plan window.

Figure 2. Plan activity for plan window
Plan activity for plan window