-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 7.0.1, 7.1.0-rc3
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v7.1, v7.0
-
Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30
-
27
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:
- causes
-
SERVER-88328 Namespace may become unavailable while sharding collection during downgrade from v7.2 to v7.0
- Closed
- is depended on by
-
SERVER-78918 Make `shardCollection` command shard authoritative
- Closed