SERVER-38191 Enforce restriction on namespace for failpoints in write_ops

This reverts commit d19bd0c883a338e4f443399c928700381c682e32.

1 files changed, 13 insertions, 4 deletions

diff --git a/jstests/noPassthrough/out_max_time_ms.js b/jstests/noPassthrough/out_max_time_ms.js
index b4d2b6f41b2..dcad3c5c071 100644
--- a/jstests/noPassthrough/out_max_time_ms.js
+++ b/jstests/noPassthrough/out_max_time_ms.js
@@ -45,11 +45,20 @@
         // use the 'maxTimeNeverTimeOut' failpoint to ensure that the operation does not
         // prematurely time out.
         const maxTimeMS = 1000 * 2;
-        const kFailPointName =
-            mode == "replaceDocuments" ? "hangDuringBatchUpdate" : "hangDuringBatchInsert";
+
         // Enable a failPoint so that the write will hang.
-        assert.commandWorked(connToHang.getDB("admin").runCommand(
-            {configureFailPoint: failPointName, mode: "alwaysOn"}));
+        let failpointCommand = {
+            configureFailPoint: failPointName,
+            mode: "alwaysOn",
+            data: {nss: kDBName + "." + kDestCollName}
+        };
+
+        // For mode "replaceCollection", the namespace of the writes will be to a temp namespace so
+        // remove the restriction on nss.
+        if (mode == "replaceCollection")
+            delete failpointCommand.data;
+
+        assert.commandWorked(connToHang.getDB("admin").runCommand(failpointCommand));
 
         // Make sure we don't run out of time before the failpoint is hit.
         assert.commandWorked(connToHang.getDB("admin").runCommand(