[SERVER-67536] Prevent transactions in move_chunk_update_shard_key_in_retryable_write.js from failing due to lock timeouts Created: 26/Jun/22  Updated: 29/Oct/23  Resolved: 28/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2022-06-27, Sharding 2022-07-11
Participants:
Linked BF Score: 45

 Description   

Increase the maxTransactionLockRequestTimeoutMillis server parameter on the shards to prevent the spurious shard version refresh for the config.system.sessions collection from causing transactions for WouldChangeOwningShard to fail with a LockTimeout error.

Note that we already did this for the other WouldChangeOwningShard jstests in SERVER-61461.



 Comments   
Comment by Githook User [ 28/Jun/22 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-67536 Prevent transactions in move_chunk_update_shard_key_in_retryable_write.js from failing due to lock timeouts
Branch: master
https://github.com/mongodb/mongo/commit/958abd27579450e032f5ee4189b4e0b2687c8b22

Generated at Thu Feb 08 06:08:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.