The collmod coordinator sends the shard server collmod command to the dbprimary for unsharded collections. If a collection's data is on a shard other than the db primary, then this command will need to be sent to both the dbprimary and the shard that owns data for the collection.

For sharded collections, we are working to broadcast the command to all shards due to the fact that moveChunk leaves behind knowledge of the collection. However, because moveCollection is based on resharding, it should not have this property. Thus, in the unsplittable case, sending the command to the dbprimary plus the shard owning data should be sufficient.

This ticket should also include testing the command for collections that are not located on the db primary and addressing any other issues with the coordinator.