summaryrefslogtreecommitdiff
path: root/jstests/sharding/run_restore.js
diff options
context:
space:
mode:
authorLucas de Castro Borges <lucas@gnuabordo.com.br>2025-02-11 15:07:35 -0300
committerLucas de Castro Borges <lucas@gnuabordo.com.br>2025-02-11 15:07:35 -0300
commit4cb8841196d0625dfa3825aa326f071cd27c7b8b (patch)
tree1682a647d4463397c119183369ae6f750d5fdcff /jstests/sharding/run_restore.js
parentaa03c6362cbaa767638e6eed9b031d86dd2643d1 (diff)
parent8f0827553e09872941945a093b647a4211a9db7f (diff)
Update upstream source from tag 'upstream/6.0.0'master
Update to upstream version '6.0.0' with Debian dir 5604a80ec1c96ca76f25f40d78e6ef855abec322
Diffstat (limited to 'jstests/sharding/run_restore.js')
-rw-r--r--jstests/sharding/run_restore.js6
1 files changed, 0 insertions, 6 deletions
diff --git a/jstests/sharding/run_restore.js b/jstests/sharding/run_restore.js
index b5dd22e10f9..3dfbd0b5b38 100644
--- a/jstests/sharding/run_restore.js
+++ b/jstests/sharding/run_restore.js
@@ -12,12 +12,6 @@
load("jstests/libs/feature_flag_util.js");
-// Because we restart nodes in standalone mode, it's possible for fast count, which doesn't
-// discriminate between majority committed data and locally committed data, and the true count,
-// which only includes majority committed data on standalones, to diverge. Therefore skip
-// validating fast count.
-TestData.skipEnforceFastCountOnValidate = true;
-
const s =
new ShardingTest({name: "runRestore", shards: 2, mongos: 1, config: 1, other: {chunkSize: 1}});