-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08
The new create collection coordinator (feature flag protected) is creating one chunk on the db primary shard when finding any error.
This could be triggered by potentially concurrent addZones that do not respect the shards where the critical section was entered.
The current handling of this situation is misleading and it may make succeed the operation (shardCollection) letting garbage in some shards (collection created) and not respecting zones.
The goal of this ticket is to, at the commit phase, the operation is permitted to skip the mustAlwaysMakeProgress and be rolled back, i.e. trigger the clean-up procedure, if it is re-calculating the parameters to execute the commit.
Involved code here.
- is depended on by
-
SERVER-80135 Allow ShardCollection to work correctly when an unsharded collection is not located on the DBPrimary
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-