[SERVER-85773] Allow cloneAsCapped to work on unsplittable collections located outside the dbPrimary Created: 26/Jan/24 Updated: 31/Jan/24 Resolved: 31/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
The cluster_clone_as_capped_command is always sending the command to the dbPrimary. However, once unsharded collections can live outside the dbPrimary, this will no longer be correct. This ticket is to change this behavior and to fix anything in the cloneAsCapped command that expects to be run on the dbPrimary. |