-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2026-07-20
-
200
-
1
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
When starting the InitializePlacementHistoryCoordinator as part of a resetPlacementHistory command, we acquire a FixedFCVRegion which we then we std::move it into the call to create the coordinator document. However FixedFCVRegion is not movable, so the std::move is a no-op (the lock is not released by the end of the statement) so the FixedFCVRegion remains held for the entire execution of the coordinator.
The FixedFCVRegion is meant to be held for a short duration (e.g. not across network calls), and holding it for longer can result in unavailability / hangs.
- is related to
-
SERVER-127968 Fix edge cases for draining of chunk operations on setFCV for Authoritative Shards
-
- Closed
-