-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.4.17
-
Component/s: Sharding
-
None
-
Sharding
-
13
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is related to
-
SERVER-29160 Sharding commonly uses write concern timeouts of 15 seconds and these are timing out in migration related operations and causing BFs
-
- Closed
-