Operational Defect Database
BugZero found this defect 108 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2564089
investigate if $out, insert and create can return LockBusy instead of MovePrimaryInProgress for unsplittable collections
Last update date:
3/12/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
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
Top User Comments
Steps to Reproduce
