[SERVER-40960] createIndexes should not automatically create collections Created: 02/May/19 Updated: 06/Dec/22 Resolved: 02/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
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. |