-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.0.0
-
Component/s: None
-
Cluster Scalability
-
Cluster Scalability Priorities
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
Today resharding/moveCollection/unshardCollection clones the indexes on the primary shard even if it's not the shard owning the collection, the indexes' definition will never get updated since the collection is resident on another shard.
resharding/moveCollection/unshardCollection should not create any index on shards that are not owning the collection.
- is related to
-
SERVER-100844 Sharding an unsharded collection fails if a stale unique index remains on the DB-primary shard
-
- Closed
-