The size of the Replicator Log is critical to the performance of replication. In the asynchronous mode of replication, due to network latency, the writes may be pending on the Primary Replicator Log. In this case, the Primary Replicator Log may overflow if the number of pending writes exceed the number of updates it can store.

When the Replicator Log overflows for a particular Secondary, the RLINK corresponding to that Secondary is marked STALE and becomes out of date until a complete resynchronization with the Primary is performed. Because resynchronization is a time-consuming process and during this time the data on the Secondary cannot be used, it is important to avoid Replicator Log overflows.