SERVER-47260 mongos_get_shard_version.js assumes causal consistency but isn't

(cherry picked from commit 6cd52288da7cfcfb9d7b2b5b850cb0c9e5f75024)

1 files changed, 7 insertions, 0 deletions

diff --git a/jstests/sharding/mongos_get_shard_version.js b/jstests/sharding/mongos_get_shard_version.js
index 1bc7031d010..3d7518822a1 100644
--- a/jstests/sharding/mongos_get_shard_version.js
+++ b/jstests/sharding/mongos_get_shard_version.js
@@ -64,6 +64,9 @@ const splitPoint = {
     y: "A".repeat(512)
 };
 
+// Run splitChunk on the shards directly since the split command for mongos doesn't have an option
+// to specify multiple split points or number of splits.
+
 let splitPoints = [];
 for (let i = 0; i < 10000; i++) {
     splitPoints.push({x: i, y: splitPoint.y});
@@ -93,6 +96,10 @@ assert.commandWorked(st.rs0.getPrimary().getDB('admin').runCommand({
     epoch: res.versionEpoch,
 }));
 
+// Perform a read on the config primary to have the mongos get the latest config optime since the
+// last two splits were performed directly on the shards.
+assert.neq(null, st.s.getDB('config').databases.findOne());
+
 // Verify that moving a chunk won't trigger mongos's routing entry to get marked as stale until
 // a request comes in to target that chunk.
 assert.commandWorked(