[SERVER-52737] Collect resource consumption metrics for capped deletes Created: 10/Nov/20 Updated: 29/Oct/23 Resolved: 20/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Brian DeLeonardis (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2020-11-16, Execution Team 2020-11-30 |
| Participants: |
| Description |
|
Capped deletions piggy-back off of normal writes. Any write operation that also performs deletes on a capped collection should collect read and write metrics for those deletes. |
| Comments |
| Comment by Githook User [ 20/Nov/20 ] |
|
Author: {'name': 'Brian DeLeonardis', 'email': 'brian.deleonardis@mongodb.com', 'username': 'bdeleonardis1'}Message: |
| Comment by Brian DeLeonardis (Inactive) [ 18/Nov/20 ] |
|
Code review: https://mongodbcr.appspot.com/718390002/ |