Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- oldshardingemea
- shardingemea-qw

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0
Sprint:
CAR Team 2025-07-21
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The disableResumableRangeDeleter server parameter is currently allowing to disable the range deleter at start-up.

This ticket is to evaluate whether it would be possible to add the capability of enabling/disabling range deletions at runtime, possibly reusing the same parameter. It should be trivial to do so for the range deleter service added in v6.2 (~~SERVER-65558~~). However, a solution targeting the legacy range deleter for backports may be more tricky.

is depended on by

SERVER-70909 Avoid range deletions while draining a shard that is being removed

Backlog

related to

SERVER-112357 moveChunk with waitForDelete hangs when range deleter is disabled

Open

SERVER-103990 Skip range deletions when transitioning from embedded to dedicated config servers

Backlog

Assignee:: Pol Pinol
Reporter:: Pierlauro Sciarelli
Participants:: Githook User, Pierlauro Sciarelli, Pol Pinol
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: May 22 2023 03:33:55 PM UTC
Updated:: Oct 13 2025 08:54:46 AM UTC
Resolved:: Jul 15 2025 09:17:06 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates