[DOCS-13510] Investigate changes in SERVER-14126: View information about the migration cleanup tasks Created: 12/Mar/20  Updated: 13/Nov/23  Resolved: 29/Apr/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.4, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-14126 View information about the migration ... Closed
Related
related to DOCS-13606 Investigate changes in SERVER-47641: ... Closed
Participants:
Days since reply: 3 years, 41 weeks ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

mongod shards only
Added a new field under shardingStatistics called 'rangeDeleterTasks'. It is an array that looks like this:
[\{shardedNs: <num>}, ...]

where <num>is the number of queued active range deleter tasks for that collection. Note that active here means that they are ready to run or running (ie, does not include pending tasks waiting for cursors to go away)

Description of Linked Ticket

Now that we don't print any status information about migration cleanups in the logs anymore, we should have a way to track at least the number of active cleanups.

One way is to expose getDeleter()>getStats()>getCurrentDeletes() in the server status.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 29/Apr/20 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-13606, DOCS-13510: 4.4 shardingStatistics.rangeDeleterTasks
Branch: master
https://github.com/mongodb/docs/commit/30aad46c07056396d2d8dd5788178dfc970fa0f0

Generated at Thu Feb 08 08:07:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.