-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-03-17
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This ticket is about replacing the collection locking/pointer acquisition via AutoGetCollection* performed in aggregations with the new Collection/ViewAcquisitions obtained via calls to acquireCollectionOrView.
- causes
-
SERVER-102587 Fix FTDC capture of config.{transactions, image_collection} collStats on secondary nodes
-
- Closed
-
- depends on
-
SERVER-100961 Integrate ShardRole with DocumentSourceCursor
-
- Closed
-
-
SERVER-101850 Implement mechanism for routers to bypass collection UUID consistency in ShardRole API for resharding relaxed=true mode
-
- Closed
-
- has to be done before
-
SERVER-102408 Clean up AutoGet-based aggregation implementation
-
- Closed
-
- is depended on by
-
SERVER-66871 Multi-collection locking must only succeed on the DB primary
-
- Backlog
-
-
SERVER-78071 A targeted query with a concurrent yield and chunk migration can miss results
-
- Closed
-
-
SERVER-76397 Remove 'VariantCollectionPtrOrAcquisition' once all read/write paths use CollectionAcquisition
-
- Backlog
-
-
SERVER-79296 Remove sharding information from CollectionPtr
-
- Backlog
-
-
SERVER-65327 AutoGetCollectionForRead should release secondary collection locks if any secondary namespace is a view or sharded, which is not supported
-
- Closed
-
-
SERVER-77571 Use acquisitions APIs instead of a CollectionPtr in plan_cache_detail::computeCollectionState
-
- Backlog
-
- is related to
-
SERVER-77507 Integrate acquisitions into Find
-
- Closed
-