SERVER-30926 Add timestamps to writes to minValid document

1 files changed, 6 insertions, 2 deletions

diff --git a/src/mongo/db/repl/replication_consistency_markers.h b/src/mongo/db/repl/replication_consistency_markers.h
index 96ea46b68c7..2bf12adb0db 100644
--- a/src/mongo/db/repl/replication_consistency_markers.h
+++ b/src/mongo/db/repl/replication_consistency_markers.h
@@ -176,12 +176,16 @@ public:
      * The applied through point is a persistent record of which oplog entries we've applied.
      * If we crash while applying a batch of oplog entries, this OpTime tells us where to start
      * applying operations on startup.
-     *
-     * If null, the applied through point is the top of the oplog.
      */
     virtual void setAppliedThrough(OperationContext* opCtx, const OpTime& optime) = 0;
 
     /**
+     * Unsets the applied through OpTime at the given 'writeTimestamp'.
+     * Once cleared, the applied through point is the top of the oplog.
+     */
+    virtual void clearAppliedThrough(OperationContext* opCtx, const Timestamp& writeTimestamp) = 0;
+
+    /**
      * You should probably be calling ReplicationCoordinator::getLastAppliedOpTime() instead.
      *
      * This reads the value from storage which isn't always updated when the ReplicationCoordinator