SERVER-42453 ensure clusterTime advances past afterClusterTime timestamp for read in step_down_on_secondary.js

1 files changed, 4 insertions, 0 deletions

diff --git a/jstests/replsets/step_down_on_secondary.js b/jstests/replsets/step_down_on_secondary.js
index 5563d4a1e23..2a5c279422b 100644
--- a/jstests/replsets/step_down_on_secondary.js
+++ b/jstests/replsets/step_down_on_secondary.js
@@ -85,6 +85,10 @@
                 "insert", {documents: [{_id: "clusterTimeAfterPrepare"}]}))
             .operationTime;
 
+    // Make sure the insert gets replicated to the old primary (current secondary) so that its
+    // clusterTime advances before we try to do an afterClusterTime read at the time of the insert.
+    rst.awaitReplication();
+
     jsTestLog("Do a read that hits a prepare conflict on the old primary");
     assert.commandWorked(
         primary.adminCommand({configureFailPoint: "WTPrintPrepareConflictLog", mode: "alwaysOn"}));