[SERVER-85407] createCollectionCoordinator should not emit shardCollection log event for unsharded collections Created: 18/Jan/24 Updated: 07/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-3364-Milestone-5 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
The create collection coordinator is used both for creating sharded and unsharded collection starting from PM-3364. In both cases the coordinator write two event in config.changelog named "shardCollection.start" and "shardCollection.end". In case the coordinator is used to create an unsharded collection we should use "createCollection.start" and "createCollection.end". |