diff options
author | Gregory Wlodarek <gregory.wlodarek@mongodb.com> | 2019-01-04 12:02:53 -0500 |
---|---|---|
committer | Gregory Wlodarek <gregory.wlodarek@mongodb.com> | 2019-01-04 12:02:53 -0500 |
commit | e4fe8b89a9ce01a3571114e9c51a4cdd725fbe1d (patch) | |
tree | 95225bc94c71e2f9439fd47cd3110fbc58f5a959 /src/mongo/db/repl/rs_rollback.cpp | |
parent | f11fb53bfd42ee53857d263407d9e555b9a1140a (diff) | |
download | mongo-e4fe8b89a9ce01a3571114e9c51a4cdd725fbe1d.tar.gz |
Revert "SERVER-38527 Merge supportsRecoverToStableTimestamp into supportsRecoveryTimestamp"
This reverts commit 804617152c5b4f89c8d54c83bdea90cb2c8541b4.
Diffstat (limited to 'src/mongo/db/repl/rs_rollback.cpp')
-rw-r--r-- | src/mongo/db/repl/rs_rollback.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
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); |