[SERVER-84091] cloneCollectionAsCapped command stops working after a replica set is bootstrapped as a sharded cluster Created: 12/Dec/23 Updated: 06/Feb/24 Resolved: 06/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Aitor Esteve Alvarado |
| 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
|
||||||||||||||||||||||||||||
| Sprint: | CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
The cloneCollectionAsCapped command is not supported through a router. As a result, the replica set endpoint needs to allow this command through the shard code paths directly. However, on upgraded replica set which is bootstrapped as a single-shard cluster, executing this command results in a CannotImplicitlyCreateCollection error with the message "Implicit collection creation on a sharded cluster must go through the CreateCollectionCoordinator".
|
| Comments |
| Comment by Pierlauro Sciarelli [ 12/Dec/23 ] |
|
The cloneCollectionAsCapped command has never been supported on sharded clusters, neither was convertToCapped. I wonder if we should simply get rid of such commands and start supporting $out to a capped collection. |