[SERVER-32719] Disallow rename when ns is not in primary shard Created: 16/Jan/18 Updated: 27/Oct/23 Resolved: 02/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.7.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | MaxH, pm-1051-legacy-tickets, sharding-wfbf-sprint | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Comments |
| Comment by Max Hirschhorn [ 02/Nov/22 ] |
|
The renameCollection command when sent through mongos is guaranteed to be routed to the primary shard of database the collection being renamed is part of. |
| Comment by Sheeri Cabral (Inactive) [ 23/Jan/20 ] |
|
What is the current behavior when this happens? |