From e4fe8b89a9ce01a3571114e9c51a4cdd725fbe1d Mon Sep 17 00:00:00 2001 From: Gregory Wlodarek Date: Fri, 4 Jan 2019 12:02:53 -0500 Subject: Revert "SERVER-38527 Merge supportsRecoverToStableTimestamp into supportsRecoveryTimestamp" This reverts commit 804617152c5b4f89c8d54c83bdea90cb2c8541b4. --- src/mongo/db/repl/rs_rollback.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/mongo/db/repl/rs_rollback.cpp') diff --git a/src/mongo/db/repl/rs_rollback.cpp b/src/mongo/db/repl/rs_rollback.cpp index f380cbc5db7..cc060b1f82c 100644 --- a/src/mongo/db/repl/rs_rollback.cpp +++ b/src/mongo/db/repl/rs_rollback.cpp @@ -616,7 +616,7 @@ void checkRbidAndUpdateMinValid(OperationContext* opCtx, // This method is only used with storage engines that do not support recover to stable // timestamp. As a result, the timestamp on the 'appliedThrough' update does not matter. - invariant(!opCtx->getServiceContext()->getStorageEngine()->supportsRecoveryTimestamp()); + invariant(!opCtx->getServiceContext()->getStorageEngine()->supportsRecoverToStableTimestamp()); replicationProcess->getConsistencyMarkers()->clearAppliedThrough(opCtx, {}); replicationProcess->getConsistencyMarkers()->setMinValid(opCtx, minValid); -- cgit v1.2.1