[SERVER-84104] document bytes written operation metric depends on update delta behavior Created: 12/Dec/23 Updated: 13/Dec/23 Resolved: 12/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
Currently, if an update ends up generating a delta WT_MODIFY instead of a full replacement, the document-bytes-written operation metric will only accrue the count of the modified bytes instead of the entire document byte count. Since the code logic to determine whether to use a delta update or a full update is internal to MongoDB, it is undesirable to leak this internal logic into the public-facing operation metric. One idea is to set the document-bytes-written metric to the change in size for the document being written, regardless of whether the entire document was replaced or not. The downstream consumers of this metric would have to recognize that this was a delta change and could be negative sometimes. |
| Comments |
| Comment by Steven Vannelli [ 12/Dec/23 ] |
|
Closing as dupe of SERVER-82839, which is where we plan to address this concern. |