[SERVER-53964] manually removing time-series buckets results in lost inserts Created: 22/Jan/21 Updated: 29/Oct/23 Resolved: 30/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: |
|
||||||||||||
| Sprint: | Execution Team 2021-01-25, Execution Team 2021-02-08 | ||||||||||||
| Participants: |
| Description |
|
There seem to be two issues at play: an insert of a measurement into a time-series collection where a bucket has been removed manually may result in a bucket update that matches no buckets, but does not generate an error even though it should. Possible solutions for this issue may include having an OpObserver invalidate buckets belonging to a time-series collections on direct operations on the bucket collection. Alternatively we can do that on detecting an error in the update. |
| Comments |
| Comment by Githook User [ 30/Jan/21 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |