[SERVER-38988] Tracked documents deleted by cleanupOrphaned in serverStatus Created: 14/Jan/19  Updated: 27/Oct/23  Resolved: 31/May/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.5
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: James Hartig Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Gone away Votes: 0
Labels: ShardingRoughEdges
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-38969 rangeDeleter stats not present in ser... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

Coming from https://jira.mongodb.org/browse/SERVER-38969

When running the `cleanupOrphaned` command. There's no way to determine how many deletions are happening and use that to estimate when it's done. When the Range Deleter was replaced with the Collection Range Deleter, the statistics were removed from serverStatus.

Instead I thought I could look at opcounters.delete and see that increasing but it is not.



 Comments   
Comment by Tommaso Tocci [ 31/May/22 ]

As of today you can use collStats to inspect the number of orphans document for a specific collection.

Comment by Eric Sedor [ 17/Jan/19 ]

Hi James, thanks for your patience.

We would not expect ".opcounters.delete" to track with documents removed because this counts operations, not documents.

But it could be appropriate to track in ".metrics.document.deleted" or another location.

We're going to evaluate this and compare against our currently planned work. Updates will be posted on this ticket as they happen.

Comment by Eric Sedor [ 15/Jan/19 ]

Hello, I wanted to let you know that we are looking into your report and appreciate your patience!

Generated at Thu Feb 08 04:50:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.