-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
Labels:None
-
Storage Execution
This has been consistently hard to work around, specifically around maintaining an exclusive lock across collection creation and index build start.
I don't believe it is worth the continued upkeep – the latest problem is from swapping db locks with collection locks in createIndexes.
This would require testing changes – particularly in concurrency suites – to deal with NamespaceNotFound errors.