SERVER-30347 Fail startup when running wiredTiger with --nojournal as part of a replica set

This reverts commit 06b9e9ebf9778293b8425093ada0aa1eb83b594e.

1 files changed, 9 insertions, 2 deletions

diff --git a/jstests/gle/gle_sharded_wc.js b/jstests/gle/gle_sharded_wc.js
index 99f3ff9cf32..bd9e29f8df7 100644
--- a/jstests/gle/gle_sharded_wc.js
+++ b/jstests/gle/gle_sharded_wc.js
@@ -11,7 +11,15 @@ TestData.skipCheckingUUIDsConsistentAcrossCluster = true;
 TestData.skipCheckDBHashes = true;
 
 (function() {
-    'use strict';
+    "use strict";
+
+    // Skip this test if running with the "wiredTiger" storage engine, since it requires
+    // using 'nojournal' in a replica set, which is not supported when using WT.
+    if (!jsTest.options().storageEngine || jsTest.options().storageEngine === "wiredTiger") {
+        // WT is currently the default engine so it is used when 'storageEngine' is not set.
+        jsTest.log("Skipping test because it is not applicable for the wiredTiger storage engine");
+        return;
+    }
 
     // Options for a cluster with two replica set shards, the first with two nodes the second with
     // one
@@ -137,5 +145,4 @@ TestData.skipCheckDBHashes = true;
     assert.eq(coll.count({_id: 1}), 1);
 
     st.stop();
-
 })();