[SERVER-68439] Concurrent drop and create could leave a view without the bucket namespace Created: 29/Jul/22 Updated: 26/Oct/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.0, 5.0.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-storex-namer | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | repro-create-drop-timeseries-bug.patch Apply the provided patch on top of commit r6.1.0-alpha-1901-g51f0bfb9163 and run jstests/noPassthrough/timeseries_create_drop_concurrent.js in the no_passthrough suite. |
||||||||
| Participants: | |||||||||
| Description |
|
The creation of a timeseries collection is achieved through the following two steps: If a drop targeting directly the bucket namespace is executed between 1 and 2 we end up with the view but without the bucket namespace. This is possible because the create collection release the locks for the bucket namespace after 1. |