SERVER-35092 do not wait for majority dummy write when writing config metadata update

(cherry picked from commit a191c2920de18ea1f32aac6559cf6288c2cfc590)

1 files changed, 0 insertions, 7 deletions

diff --git a/src/mongo/db/s/shard_server_catalog_cache_loader.cpp b/src/mongo/db/s/shard_server_catalog_cache_loader.cpp
index 069685b1595..09b17d07346 100644
--- a/src/mongo/db/s/shard_server_catalog_cache_loader.cpp
+++ b/src/mongo/db/s/shard_server_catalog_cache_loader.cpp
@@ -655,13 +655,6 @@ std::pair<bool, CollectionAndChangedChunks> ShardServerCatalogCacheLoader::_getE
 
 Status ShardServerCatalogCacheLoader::_ensureMajorityPrimaryAndScheduleTask(
     OperationContext* opCtx, const NamespaceString& nss, Task task) {
-    Status linearizableReadStatus = waitForLinearizableReadConcern(opCtx);
-    if (!linearizableReadStatus.isOK()) {
-        return {linearizableReadStatus.code(),
-                str::stream() << "Unable to schedule routing table update because this is not the"
-                              << " majority primary and may not have the latest data. Error: "
-                              << linearizableReadStatus.reason()};
-    }
 
     stdx::lock_guard<stdx::mutex> lock(_mutex);
     const bool wasEmpty = _taskLists[nss].empty();