From 803e6ba5c7c4a13d9978d9adb32c68cd95f7c1e0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20Jos=C3=A9=20Grillo=20Ramirez?= Date: Mon, 20 Jun 2022 13:41:24 +0000 Subject: SERVER-64717 Ensure the ShardRegistry always read with majority write concern, even in the config server --- src/mongo/db/repl/rs_rollback.cpp | 8 -------- 1 file changed, 8 deletions(-) (limited to 'src/mongo/db/repl') diff --git a/src/mongo/db/repl/rs_rollback.cpp b/src/mongo/db/repl/rs_rollback.cpp index bca10b5c3ed..8777903803c 100644 --- a/src/mongo/db/repl/rs_rollback.cpp +++ b/src/mongo/db/repl/rs_rollback.cpp @@ -2012,14 +2012,6 @@ void rollback_internal::syncFixUp(OperationContext* opCtx, validator->resetKeyManagerCache(); } - // Force the config server to update its shard registry on next access. Otherwise it may have - // the stale data that has been just rolled back. - if (serverGlobalParams.clusterRole == ClusterRole::ConfigServer) { - if (auto shardRegistry = Grid::get(opCtx)->shardRegistry()) { - shardRegistry->clearEntries(); - } - } - // Force the default read/write concern cache to reload on next access in case the defaults // document was rolled back. ReadWriteConcernDefaults::get(opCtx).invalidate(); -- cgit v1.2.1