Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2025-09-29
CAR Domain/s:

🟦 Shard Catalog

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

After ~~SERVER-76397~~ is completed there should be no more AutoGetCollection usages on multiple namespaces.
We can stop supporting the feature and delete the related code.
Multi-namespace acquisitions should only be supported by the shard role API.

is depended on by

SERVER-66871 Multi-collection locking must only succeed on the DB primary

Closed

is related to

SERVER-76397 Remove 'VariantCollectionPtrOrAcquisition' once all read/write paths use CollectionAcquisition

Closed

related to

SERVER-66871 Multi-collection locking must only succeed on the DB primary

Closed

Assignee:: Enrico Golfieri
Reporter:: Enrico Golfieri
Participants:: Enrico Golfieri, Githook User
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Sep 15 2025 10:23:08 AM UTC
Updated:: Sep 19 2025 08:14:42 AM UTC
Resolved:: Sep 19 2025 08:14:43 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates