[SERVER-83774] Create collection coordinator should clean up the collection on the db primary shard in case of rollback Created: 01/Dec/23 Updated: 06/Feb/24 |
|
| Status: | In Code Review |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Pol Pinol |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | car-qw, robust-create-collection | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | CAR Team 2024-01-08, CAR Team 2024-02-05, CAR Team 2024-02-19 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
There are cases where the create collection coordinator creates the collection in the db primary shard, and then, due to a non retriable errors we need to rollback. In case the coordinator has created the local collection, i.e. the collection did not previously exist, it must drop it to proceed with a clean rollback. It is important to only drop the collection when it has been created by the create collection coordinator. |