[SERVER-37377] Consider increasing default distributed lock timeout Created: 28/Sep/18  Updated: 06/Dec/22  Resolved: 29/Jul/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.17
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-29160 Sharding commonly uses write concern ... Closed
Assigned Teams:
Sharding
Participants:
Linked BF Score: 13

 Description   

The default timeout for grabbing the distributed lock is 20 seconds and in test suites with CSRS stepdowns, attempts to take the lock can time out and fail tests, especially on slower platforms.

This is more of an issue in earlier releases, like 3.4, where more metadata commands run on mongos.


Generated at Thu Feb 08 04:45:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.