[SERVER-38969] rangeDeleter stats not present in serverStatus Created: 13/Jan/19  Updated: 27/Oct/23  Resolved: 14/Jan/19

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

Type: Bug Priority: Minor - P4
Reporter: James Hartig Assignee: Danny Hatcher (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-12358 Remove references to Range Deleter Closed
Problem/Incident
is caused by SERVER-27760 Replace RangeDeleter with CollectionR... Closed
Related
related to SERVER-38988 Tracked documents deleted by cleanupO... Closed
Operating System: ALL
Steps To Reproduce:

Run cleanupOrphaned command

Run `db.serverStatus({rangeDeleter: 1})`

Example the following prints nothing.

mongo --eval 'db.serverStatus({rangeDeleter: 1})' | grep rangeDeleter

Yet:

mongo --eval 'db.currentOp(true)'
{
"host" : "phil.11-e.ninja:27017",
"desc" : "Collection Range Deleter",
"active" : true,
"currentOpTime" : "2019-01-13T05:49:44.398+0000",
"opid" : 233405453,
"op" : "none",

...

 

Participants:

 Description   

Despite the docs saying that the `rangeDeleter` stats should be visible when running `db.serverStatus({rangeDeleter: 1})`, there is no top-level `rangeDeleter` or any mention of it.



 Comments   
Comment by James Hartig [ 14/Jan/19 ]

The log only tells you when it's finished. The cleanupOrphaned command I ran needs to delete over 100 million documents and I was trying to figure out an estimate of how long it would take. The stats would've been useful in determining that. Fortunately, I can use the opcountersRepl.delete to determine that it's going to take over 4 days to complete but that's a roundabout way of doing it, and wouldn't be accurate if our application regularly performed deletes.

Comment by Danny Hatcher (Inactive) [ 14/Jan/19 ]

If you'd like to confirm that the cleanupOrphaned command ran, the mongod log files will let you know.

Comment by Danny Hatcher (Inactive) [ 14/Jan/19 ]

Hello James,

The "Range Deleter" functionality was replaced by the "Collection Range Deleter" you see in currentOp via SERVER-27760. There was a decision not to replace the statistics as they were deemed not very useful. It appears that the section was not removed from our documentation so I will file a ticket to do so.

Could you create a separate ticket for the discrepancy that you see with the delete opcounters so that we can triage it separately?

Thank you,

Danny

Comment by James Hartig [ 13/Jan/19 ]

Not sure if its a separate bug, but the `opcounters.delete` field is not going up either. But if I look at the secondaries in the same replica set, their `opcountersRepl.delete` number is going up.

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