[SERVER-86074] investigate if $out, insert and create can return LockBusy instead of MovePrimaryInProgress for unsplittable collections Created: 01/Feb/24  Updated: 02/Feb/24

Status: Needs Scheduling
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Enrico Golfieri Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-81190 Support tracking "simple" unsharded c... Closed
Assigned Teams:
Catalog and Routing
Operating System: ALL
Participants:

 Description   

After SERVER-81190 any implicit collection creation will happen within the CreateCollectonCoordinator. 

This causes the shardsvrCreateCollection (and therefore the caller) to fail with "LockBusy" in case a concurrent operation is in progress. 

Specifically for the movePrimary, a special error "movePrimaryInProgress" is thrown for this case by specific operation such as createIndex.

Insert, $out and "create" used to return movePrimaryInProgress and now return LockBusy.

The goal of this ticket is to investigate whether is ok to now return LockBusy or instead movePrimaryInProgress should be enforced for back-compatibility


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