summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAntonio Fuschetto <antonio.fuschetto@mongodb.com>2022-11-15 15:24:26 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2022-11-15 15:53:23 +0000
commit8fa43ad1a9e9cae6133e3d0a924a07054e8fd70c (patch)
treeeab6bb3d2fb58fd7b4aa992151d1fa2550e0b9c6
parent46c324dbbac641206a010e0c2b8cbea24dbd3b4e (diff)
downloadmongo-8fa43ad1a9e9cae6133e3d0a924a07054e8fd70c.tar.gz
SERVER-67862 Make ShardingStateRecovery::endMetadataOp() persist the configTime as a preliminary step for removing ShardingStateRecovery
-rw-r--r--src/mongo/db/s/migration_source_manager.cpp3
-rw-r--r--src/mongo/db/s/move_primary_source_manager.cpp3
2 files changed, 0 insertions, 6 deletions
diff --git a/src/mongo/db/s/migration_source_manager.cpp b/src/mongo/db/s/migration_source_manager.cpp
index 70dc1982829..413bd81f5c2 100644
--- a/src/mongo/db/s/migration_source_manager.cpp
+++ b/src/mongo/db/s/migration_source_manager.cpp
@@ -357,9 +357,6 @@ void MigrationSourceManager::enterCriticalSection() {
uassertStatusOKWithContext(ShardingStateRecovery_DEPRECATED::startMetadataOp(_opCtx),
"Start metadata op");
- // Checkpoint the vector clock to ensure causality in the event of a crash or shutdown.
- VectorClockMutable::get(_opCtx)->waitForDurableConfigTime().get(_opCtx);
-
LOGV2_DEBUG_OPTIONS(4817402,
2,
{logv2::LogComponent::kShardMigrationPerf},
diff --git a/src/mongo/db/s/move_primary_source_manager.cpp b/src/mongo/db/s/move_primary_source_manager.cpp
index 997b9605ead..350198d53ce 100644
--- a/src/mongo/db/s/move_primary_source_manager.cpp
+++ b/src/mongo/db/s/move_primary_source_manager.cpp
@@ -163,9 +163,6 @@ Status MovePrimarySourceManager::enterCriticalSection(OperationContext* opCtx) {
return startMetadataOpStatus;
}
- // Checkpoint the vector clock to ensure causality in the event of a crash or shutdown.
- VectorClockMutable::get(opCtx)->waitForDurableConfigTime().get(opCtx);
-
{
// The critical section must be entered with the database X lock in order to ensure there
// are no writes which could have entered and passed the database version check just before