[SERVER-80134] Allow CollMod to work when an unsharded collection is not located on the DBPrimary Created: 16/Aug/23 Updated: 29/Oct/23 Resolved: 21/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 21/Sep/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |