diff options
author | Jason Zhang <jason.zhang@mongodb.com> | 2020-09-17 21:42:04 +0000 |
---|---|---|
committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2020-12-04 17:22:25 +0000 |
commit | e6a07717382eb87264f8ba63462000f8e6a582dc (patch) | |
tree | 42188db51b9835e785988782d3c1893f7317c859 | |
parent | f9bbf746602f00b8ad41979c27561ee7a8829630 (diff) | |
download | mongo-e6a07717382eb87264f8ba63462000f8e6a582dc.tar.gz |
SERVER-50900 Disable PeriodicShardedIndexConsistencyChecker for cursor_valid_after_shard_stepdown.js
(cherry picked from commit eaa9b518099c250cbb3083ed84636922a5b29feb)
-rw-r--r-- | jstests/sharding/cursor_valid_after_shard_stepdown.js | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/jstests/sharding/cursor_valid_after_shard_stepdown.js b/jstests/sharding/cursor_valid_after_shard_stepdown.js index c26de68b8c6..e70cfcde1b8 100644 --- a/jstests/sharding/cursor_valid_after_shard_stepdown.js +++ b/jstests/sharding/cursor_valid_after_shard_stepdown.js @@ -8,6 +8,12 @@ TestData.skipCheckingUUIDsConsistentAcrossCluster = true; var st = new ShardingTest({shards: 1, rs: {nodes: 2}}); +// This test expects the shard version after step down to be UNKNOWN. Disable checking for index +// consistency to ensure that the config server doesn't trigger a StaleShardVersion exception on +// shard0 and cause it to refresh its sharding metadata. +st._configServers.forEach( + config => config.adminCommand({setParameter: 1, enableShardedIndexConsistencyCheck: false})); + assert.commandWorked(st.s0.adminCommand({enablesharding: 'TestDB'})); st.ensurePrimaryShard('TestDB', st.shard0.shardName); assert.commandWorked(st.s0.adminCommand({shardcollection: 'TestDB.TestColl', key: {x: 1}})); |