-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
Affects Version/s: 9.0.0-rc0, 9.1.0-rc0
-
Component/s: Sharding, Upgrade/Downgrade
-
Catalog and Routing
-
v9.0
-
CAR Team 2026-08-03, CAR Team 2026-08-17
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Under the Authoritative Shards model, the DSS and CSS should always contain correct (i.e. not stale) metadata, and DDLs could be taking advantage of that. However bugs (SERVER-132477) or transitional setFCV states (SERVER-132505) could break this assumption.
This ticket should find usages of the DSS/CSS in DDLs and reason about their correctness/risk.
- is related to
-
SERVER-132505 Auth shards may encounter stale metadata from the legacy refresh sharding metadata
-
- In Progress
-
-
SERVER-132477 movePrimary does not clear CSR state for untracked collections
-
- Closed
-