-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2026-04-27, CAR Team 2026-05-11
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Several DDLs that already commit to the shard catalog (create, drop, refine) currently do not mark the CSS as authoritative.
This was intentionally deferred because Evergreen patches were not fully green, with separate tickets tracking the outstanding failures.
Once those dependencies are resolved, this ticket should be executed to flip the CSS to authoritative on those DDL paths.
- depends on
-
SERVER-125053 many_txns.js fails in analyze_shard_key_jscore_passthrough
-
- Open
-
-
SERVER-123832 StaleConfig failure in $lookup when foreign collection is dropped and recreated on a different shard
-
- Closed
-
-
SERVER-123844 Address the configTime liveness issue in the authoritative refresh path
-
- Closed
-
-
SERVER-124505 CollectionCacheRecoverer uses gap-intolerant RoutingTableHistory constructor
-
- Closed
-
-
SERVER-125628 Chunk operations should leave shard catalog metadata non-authoritative
-
- In Code Review
-
-
SERVER-125615 refineCollectionShardKey should install authoritative shard catalog metadata on the DB primary even when it owns no chunks
-
- Closed
-
- is depended on by
-
SERVER-124366 Delete _internalClearCollectionShardingMetadata command
-
- Blocked
-
- related to
-
SERVER-125690 timeseries_create_indexes.js in concurrency_sharded_replication_with_balancer
-
- In Progress
-