-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
v7.3, v7.2
-
Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5
-
13
-
3
As part of SERVER-75580, _applyInsertOrUpdate is modified to run the collection lock acquisition function as a callback to OperationContext::runWithDeadline with deadline of gReshardingOplogApplierMaxLockRequestTimeoutMillis which has a default value of 5ms. This sets a deadline of lock acquisition to the whole function call back incorrectly, as the deadline is meant specifically for time to acquire the collection lock. This happens at multiple places in other applyOp functions and need to be fixed.
- is caused by
-
SERVER-75580 Thread-through `ScopedCollectionOrViewAcquisition` on the internal delete code paths
- Closed