SERVER-49523 Use a 3-node replica set for 'commit_quorum_does_not_hang_with_initial_sync.js' to avoid having the primary stepdown if it can't see a majority of the replica set

1 files changed, 6 insertions, 4 deletions

diff --git a/jstests/noPassthrough/commit_quorum_does_not_hang_with_initial_sync.js b/jstests/noPassthrough/commit_quorum_does_not_hang_with_initial_sync.js
index 17b7cd2da75..9bee3a46b65 100644
--- a/jstests/noPassthrough/commit_quorum_does_not_hang_with_initial_sync.js
+++ b/jstests/noPassthrough/commit_quorum_does_not_hang_with_initial_sync.js
@@ -34,6 +34,12 @@ const rst = new ReplSetTest({
                 priority: 0,
             },
         },
+        {
+            // Disallow elections on secondary.
+            rsConfig: {
+                priority: 0,
+            },
+        },
     ]
 });
 
@@ -111,10 +117,6 @@ function checkForIndexes(indexes) {
 }
 checkForIndexes(["b_1", "c_1", "d_1", "e_1", "f_1", "g_1"]);
 
-// Checks that the index specs have the proper grouping by ensuring that we only start 3 index
-// builder threads.
-checkLog.containsWithCount(secondary, "Index build: initialized", 3);
-
 assert.commandWorked(
     secondary.adminCommand({configureFailPoint: "initialSyncHangAfterDataCloning", mode: "off"}));