SERVER-43918 Fix 'compound_hashed_shard_key.js' test flakiness

1 files changed, 7 insertions, 0 deletions

diff --git a/jstests/multiVersion/compound_hashed_shard_key.js b/jstests/multiVersion/compound_hashed_shard_key.js
index 68abcb3e050..7e3909c56b2 100644
--- a/jstests/multiVersion/compound_hashed_shard_key.js
+++ b/jstests/multiVersion/compound_hashed_shard_key.js
@@ -14,6 +14,13 @@ load("jstests/multiVersion/libs/multi_cluster.js");  // upgradeCluster.
 
 TestData.skipCheckDBHashes = true;  // Skip db hashes when restarting the replset.
 
+// When checking UUID consistency, the shell attempts to run a command on the node it believes is
+// primary in each shard. However, this test restarts shards, and the node that is elected primary
+// after the restart may be different from the original primary. Since the shell does not retry on
+// NotMaster errors, and whether or not it detects the new primary before issuing the command is
+// nondeterministic, skip the consistency check for this test.
+TestData.skipCheckingUUIDsConsistentAcrossCluster = true;
+
 const nodeOptions42 = {
     binVersion: "last-stable"
 };