[DOCS-16232] [SERVER] Investigate changes in SERVER-70036: Investigate deprioritizing the range deleter Created: 30/Jun/23  Updated: 13/Nov/23  Resolved: 01/Aug/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc7, 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: Kanchana Sekhar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
documents SERVER-70036 Investigate deprioritizing the range ... Closed
Participants:
Days since reply: 27 weeks, 6 days ago
Story Points: 3

 Description   
Original Downstream Change Summary

Starting from v7.0, a new configurable server parameter `rangeDeleterHighPriority` is present on mongod , taking effect only on sharded clusters.

This is the description: "By default, this parameter is set to 'false' meaning that orphaned documents cleanup have a lower priority than user operations. Setting this parameter to true prioritizes their deletion over user operations."

Description of Linked Ticket

The range deleter can serve as a long running background task that causes lag in user operations when the system is under heavy load. Explore deprioritizing range deletions and the imapact



 Comments   
Comment by Kanchana Sekhar [ 27/Jul/23 ]

PR: https://github.com/10gen/docs-mongodb-internal/pull/4161

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