[SERVER-60105] Inserts into timeseries collections are not observable from any opcounter Created: 21/Sep/21 Updated: 29/Oct/23 Resolved: 07/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.2, 5.0.8, 6.0.0-rc0 |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Halvor Strand | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | time-series | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v5.3, v5.0
|
||||
| Sprint: | Execution Team 2021-11-29, Execution Team 2021-12-13, Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-01-24, Execution Team 2022-02-07, Execution Team 2022-02-21, Execution Team 2022-03-07, Execution Team 2022-04-18 | ||||
| Participants: | |||||
| Description |
|
Doing inserts into a time series does not increase the `insert` count of `mongostat`. Having a way to track these `insert`s would be a great addition. The `net_in` column does reflect the increase in traffic, but is a bit more obfuscated as a metric for inserts. Experienced using mongostat 100.5.0 and MongoDB 5.0.2. |
| Comments |
| Comment by Githook User [ 08/Apr/22 ] | ||||||||||||
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 0e7af76ae586749bf71928963c857cb50f760b9b) | ||||||||||||
| Comment by Githook User [ 08/Apr/22 ] | ||||||||||||
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 0e7af76ae586749bf71928963c857cb50f760b9b) | ||||||||||||
| Comment by Githook User [ 07/Apr/22 ] | ||||||||||||
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: | ||||||||||||
| Comment by Edwin Zhou [ 11/Oct/21 ] | ||||||||||||
|
Hi halvor.holsten.strand@gmail.com, Thanks for your report. I've been able to reproduce the issue and I will pass this on to the appropriate team for investigation.
Best, | ||||||||||||
| Comment by Halvor Strand [ 21/Sep/21 ] | ||||||||||||
|
Thanks @Tim Fogarty. I'll just add that the `update` counter also does not increase from my experience. I'd expect that counter to be higher. | ||||||||||||
| Comment by Tim Fogarty [ 21/Sep/21 ] | ||||||||||||
|
Hi halvor.holsten.strand@gmail.com, timeseries collections are implemented as a writable non-materialized view over an internal system collection. Multiple timeseries measurements are bucketed into documents in the internal system collection. So when you insert into a timeseries collection, most of the time that will be an update to an internal bucket document, not an insert. There will only be an insert when a new bucket document is created. So I think that's why you're seeing the current behavior. mongostat reports whatever the opcounters in the serverStatus command reports. So I'm going to move this ticket to the SERVER project. The Server Team will be able to let you know if we have any plans to change the serverStatus behavior for timeseries collections.
|