[SERVER-81353] Add a clean up procedure to the create collection coordinator Created: 22/Sep/23  Updated: 26/Oct/23  Resolved: 26/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 7.0.1, 7.1.0-rc3
Fix Version/s: 7.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Pol Pinol Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-78918 Make `shardCollection` command shard ... Closed
Assigned Teams:
Catalog and Routing
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.1, v7.0
Sprint: Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30
Participants:

 Description   

The current implementation of the create collection coordinator does not guarantee a clean exit when receiving a non-retriable error. We are doing a best effort to release the critical section, without any guarantee that it is going to succeed (onError from create_collection_coordinator.cpp).

The goal of this ticket is to add a new clean up procedure on abort that guarantees that before exiting the create collection we will, at least, release the critical section and possibly remove orphaned collections on the participants.

This work is similar to what the move primary coordinator introduced:



 Comments   
Comment by Githook User [ 26/Oct/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-81353 Add a clean up procedure to the create collection coordinator
Branch: master
https://github.com/mongodb/mongo/commit/98b69b3b7b67200ad852d5fe5b07d309b414b276

Generated at Thu Feb 08 06:46:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.