summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornandinibhartiyaMDB <104035932+nandinibhartiyaMDB@users.noreply.github.com>2024-09-16 16:15:44 -0500
committerMongoDB Bot <mongo-bot@mongodb.com>2024-09-16 21:52:39 +0000
commit4cbb7cd57170be42d1bc91f2bfe78fa499d19260 (patch)
tree0b182604a873bf6b992ce81ff04e4d80c766f946
parent79c858bba5e11569ccb3dcb000159761719adcbc (diff)
SERVER-94665: Increase lock acquisition timeout (#27131)
GitOrigin-RevId: 838bbbaafd48ac5722c0ae6c3480858730795a82
-rw-r--r--jstests/sharding/txn_commit_optimizations_for_read_only_shards.js7
1 files changed, 7 insertions, 0 deletions
diff --git a/jstests/sharding/txn_commit_optimizations_for_read_only_shards.js b/jstests/sharding/txn_commit_optimizations_for_read_only_shards.js
index d399e6a5536..a4f7576e9cf 100644
--- a/jstests/sharding/txn_commit_optimizations_for_read_only_shards.js
+++ b/jstests/sharding/txn_commit_optimizations_for_read_only_shards.js
@@ -73,6 +73,13 @@ let st = new ShardingTest({
shards: 3,
// Create shards with more than one node because we test for writeConcern majority failing.
config: TestData.configShard ? undefined : 1,
+ rsOptions: {
+ setParameter: {
+ // Set this to higher than the deault 5ms to avoid failures due to not being able to
+ // acquire the lock quickly enough.
+ maxTransactionLockRequestTimeoutMillis: ReplSetTest.kDefaultTimeoutMS,
+ }
+ },
other: {
// The name of the shards affects the ordering of which shard will be targeted first
// for broadcast operations so always use the same names for each test run.