SERVER-42091 Look for at least 2 log messages in flow_control_logging.js

1 files changed, 5 insertions, 4 deletions

diff --git a/jstests/noPassthrough/flow_control_logging.js b/jstests/noPassthrough/flow_control_logging.js
index e15186654d8..0d4744b4559 100644
--- a/jstests/noPassthrough/flow_control_logging.js
+++ b/jstests/noPassthrough/flow_control_logging.js
@@ -42,10 +42,11 @@
     // oplog entry every other second. Once the primary notices the sustainer rate is not moving, it
     // should start logging a warning once per second. This check waits for two log messages to make
     // sure the appropriate state variables are being reset.
-    checkLog.containsWithCount(replSet.getPrimary(),
-                               "Flow control is engaged and the sustainer point is not moving.",
-                               2,
-                               timeoutMilliseconds);
+    checkLog.containsWithAtLeastCount(
+        replSet.getPrimary(),
+        "Flow control is engaged and the sustainer point is not moving.",
+        2,
+        timeoutMilliseconds);
 
     // Restart replication so the replica set will shut down.
     for (let sec of replSet.getSecondaries()) {