[SERVER-45111] Expose more granular stats about TTL deletions Created: 12/Dec/19 Updated: 07/Sep/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Ivan Grigolon | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
With the value serverstatus.metrics.ttl.deletedDocuments we can know the total number of documents deleted from collections with a ttl index (in other words we combine all the documents deleted by every TTL index in one value) We should introduce metrics on "per TTL index" so that we can differentiate how many document are deleted by each TTL index. |
| Comments |
| Comment by Dayo Lasode [ 16/Dec/19 ] |
|
This will be a useful metric at the document level to help review document turnover |
| Comment by Bruce Lucas (Inactive) [ 13/Dec/19 ] |
|
As far as I know we don't currently have any per-namespace information in serverStatus. This could potentially be a very large number of fields, which could be a problem for ftdc. Maybe this information would be more at home in collStats. If it is put into serverStatus, it would be good to make it optional and excluded from ftdc. |
| Comment by Carl Champain (Inactive) [ 13/Dec/19 ] |
|
Passing this ticket along to the Query team. |