-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 7.2.0-rc0
-
Component/s: None
-
Sharding EMEA
-
Fully Compatible
-
ALL
-
v7.1, v7.0, v6.0
-
Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02
-
3
Collmod is designed to be propagated to all the shards owning chunks and to the DBPrimary shard (that's because we need to keep a copy of the collection metadata on the DBPrimary for design purposes).
However, the createIndex command is only targeting all the shards owning chunks, skipping the DBPrimary if it doesn't own any chunks.
So, if a collmod is called over an index that is not present on the DBPrimary, it will fail with a NoIndexFound error.
- is caused by
-
SERVER-71819 Broadcast collMod command to all shards
- Closed
- is depended on by
-
SERVER-80134 Allow CollMod to work when an unsharded collection is not located on the DBPrimary
- Closed
- is related to
-
SERVER-62310 collMod command not sent to all shards for a sharded collection if no chunks have been received
- Closed
-
SERVER-90117 Interrupting collMod can leave behind inconsistent collection options
- Closed