[SERVER-74438] MetaField is being added to the control block of time-series buckets Created: 28/Feb/23 Updated: 29/Oct/23 Resolved: 06/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 6.3.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Fausto Leyva (Inactive) | Assignee: | Fausto Leyva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v6.3
|
||||
| Steps To Reproduce: | 1. ) const docs = [\{"time": new Date(), "tag": i},...]; // array of 1000 measurements with increasing metaField |
||||
| Sprint: | Execution Team 2023-03-06, Execution Team 2023-03-20 | ||||
| Participants: | |||||
| Description |
|
I noticed in jstests/concurrency/fsm_workloads/timeseries_insert_idle_bucket_expiration.js we can arrive to this invalid state:
For some reason we are adding the metaField value to the control block. Possibly in the process of reopening buckets and inserting more measurements into it. |
| Comments |
| Comment by Githook User [ 07/Mar/23 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: (cherry picked from commit 1e217fd954eefda95d9d8f8907f077b0aa379667) |
| Comment by Githook User [ 06/Mar/23 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |