-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
Repl 2018-09-10, Repl 2018-09-24, Repl 2019-02-25, Storage NYC 2019-03-25
If the oldest oplog entries are truncated, replication recovery may not be able to succeed. We are recommending that backup services insert into the oplog as a standalone so replication can do its own recovery to a point-in-time, but this requires that the oplog can grow indefinitely.
- is related to
-
SERVER-36494 Prevent oplog truncation of oplog entries needed for startup recovery
- Closed
-
SERVER-39679 Add callback to replication when storage takes a checkpoint to learn of the maximum oplog truncation timestamp
- Closed