SERVER-57606 Define the default read concern to available in sharding_rs2.js

1 files changed, 9 insertions, 4 deletions

diff --git a/jstests/sharding/sharding_rs2.js b/jstests/sharding/sharding_rs2.js
index 6d27bc899f7..ea5b8a7760c 100644
--- a/jstests/sharding/sharding_rs2.js
+++ b/jstests/sharding/sharding_rs2.js
@@ -38,10 +38,15 @@ var db = s.getDB("test");
 var t = db.foo;
 
 assert.commandWorked(s.s0.adminCommand({enablesharding: "test"}));
-// The default WC is majority and fsyncLock will prevent satisfying any majority writes.
-assert.commandWorked(s.s.adminCommand(
-    {setDefaultRWConcern: 1, defaultWriteConcern: {w: 1}, writeConcern: {w: "majority"}}));
-
+// The default WC is 'majority' and fsyncLock will prevent satisfying any majority writes.
+// The default RC is 'local' but fsync will block any refresh on secondaries, that's why RC is
+// defaulted to 'available'.
+assert.commandWorked(s.s.adminCommand({
+    setDefaultRWConcern: 1,
+    defaultReadConcern: {level: "available"},
+    defaultWriteConcern: {w: 1},
+    writeConcern: {w: "majority"}
+}));
 s.ensurePrimaryShard('test', s.shard0.shardName);
 
 // -------------------------------------------------------------------------------------------