[SERVER-73094] Add and test ability for timeseries deletes to intermingle with concurrent inserts. Created: 19/Jan/23 Updated: 29/Oct/23 Resolved: 22/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Alyssa Clark |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Execution Team 2023-02-20 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 50 | ||||||||||||||||
| Description |
|
We're worried about race conditions in the bucket catalog, and should test that (a) all measurements visible at the time of the delete can be found and deleted eventually (after internal retrying) and (b) any measurements being inserted during the delete should show up and remain after the delete if they don't match the query predicate (particularly focused on those that would end up in an affected bucket) |
| Comments |
| Comment by Githook User [ 22/Mar/23 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |
| Comment by Githook User [ 21/Mar/23 ] |
|
Author: {'name': 'Alyssa Wagenmaker', 'email': 'alyssa.wagenmaker@mongodb.com', 'username': 'awagenmaker'}Message: |