-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.0.0, 8.2.0
-
Component/s: None
-
None
-
Catalog and Routing
-
3
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
Scenario:
- Shard A is the primay shard for db
- Unsharded db.coll has been placed on shard B (via moveCollection)
- $out writing to the same collection db.coll creates it on shard A (that is the primary shard) rather than shard B (that is the shard it used to live on).
This ticket is to ensure that $out recreates the unsharded collection on the same shard as it existed before.
- related to
-
SERVER-79718 Remove HostTypeRequirement::kPrimaryShard from $out
-
- Closed
-
-
SERVER-87554 Move non-8.0 required work to featureFlagTrackUnshardedCollectionsUponCreation
-
- Closed
-
-
SERVER-98504 Remove any usage of trackUnshardedUponCreation feature flag
-
- Closed
-