[SERVER-78497] Drop index may not consider a timeseries collection due to a concurrent create timeseries collection Created: 28/Jun/23 Updated: 22/Nov/23 Resolved: 22/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.0, 6.1.0, 7.0.0-rc5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Allison Easton |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, CAR Team 2023-11-13, CAR Team 2023-11-27 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Story Points: | 2 | ||||||||||||||||
| Description |
|
Drop index may not consider a timeseries collection if the create of a timeseries collection happen after the timeseries collection check during the drop index execution. |
| Comments |
| Comment by Allison Easton [ 22/Nov/23 ] |
|
The ordering of the ddl lock acquisition and the timeseries namespace resolution was already changed by |