[SERVER-69358] Report data size increase in updateWithDamages Created: 01/Sep/22 Updated: 29/Oct/23 Resolved: 20/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2022-10-03 | ||||
| Participants: | |||||
| Linked BF Score: | 122 | ||||
| Description |
|
The doUpdateWithDamages method in the WiredTiger RecordStore is not reporting the data size change whenever we update with damages. This leads to invalid metrics related to collection size. The reported change should be the same as the one in doUpdateRecord. |
| Comments |
| Comment by Githook User [ 20/Sep/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |
| Comment by Jordi Olivares Provencio [ 01/Sep/22 ] |
|
Note that this is not a concern now as the method is only called if the document can be updated in place. That is, if the document size doesn't change which would not cause a size change of the collection. |