-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23
With the Sharding-First Catalog work, the CollectionPtr becomes the single object representing the snapshot state of a given collection, against which upper layers of the core server (e.g., Query) will program.
This ticket is about implementing that infrastructure along with the relevant functions for its maintenance.
Once this ticket is completed, we will have a single library and entry-point for obtaining collection snapshots and that entry-point will become the input for construction of {{CollectionPtr}}s.
- causes
-
SERVER-73137 Coverity analysis defect 134897: Uninitialized scalar field
- Closed
-
SERVER-73434 Investigate failures on multi_statement_transaction_simple_majority_writes.js in suites with balancer on
- Closed
- depends on
-
SERVER-69434 Make the DSS acquisition a RAII
- Closed
-
SERVER-69435 Make the CSS acquisition a RAII
- Closed
-
SERVER-69483 Merge the db_raii and catalog_raii libraries into a single library
- Closed
-
SERVER-71782 PoC the insert path using the CollectionSnapshots API
- Closed
- is depended on by
-
SERVER-64128 Investigate behavior when query against unsharded collection runs concurrently with shardCollection and moveChunk
- Blocked
-
SERVER-71784 Support lock-free in CollectionSnapshots acquisition
- Closed
-
SERVER-73004 Add support to CollectionSnapshot for locking multiple collections without recursively locking db lock
- Closed
-
SERVER-73005 Support view acquisition on CollectionSnapshot API
- Closed