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: None
Labels:
- range-deleter-improvements

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, ClusterScalability Mar31-Apr14, ClusterScalability Apr28-May09
Linked BF Score:
200
Confidence Status:
None
Work Order:
3

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

The new BatchedDeleteStage deletes documents efficiently in batches.

Dependencies that I'm aware of to switch the range deleter from the DeleteStage to the BatchedDeleteStage:

Support for the fromMigrate parameter: depends on ~~SERVER-64107~~ which in turns depends on ~~SERVER-65859~~.
Support for the returnDeleted parameter.
Support for the removeSaver parameter (for moveParanoia).

depends on

SERVER-77543 Support `fromMigrate` in batched delete stage

Closed

SERVER-103310 Support the fromMigrate parameter in BatchedDeleteStage

Closed

SERVER-103311 Support the returnDeleted parameter in the BatchedDeleteStage

Closed

SERVER-103312 Support the removeSaver parameter (for moveParanoia) in BatchedDeleteStage

Closed

is duplicated by

SERVER-67331 Use efficient multi-deletes for range deletions

Closed

SERVER-72298 Use batch deletions to delete orphaned ranges

Closed

related to

SERVER-78661 Complete TODO listed in SERVER-66279

Closed

SERVER-72776 Get rid of `moveParanoia` code

Closed

(1 is duplicated by, 2 related to)

Assignee:: Ben Gawel

Reporter:: Josef Ahmad

Participants:: Ben Gawel, Garaudy Etienne, Githook User, Josef Ahmad, Louis Williams, Pierlauro Sciarelli

Votes:: 0 Vote for this issue

Watchers:: 21 Start watching this issue

Created:: May 06 2022 02:54:29 PM UTC

Updated:: May 05 2025 06:13:23 PM UTC

Resolved:: May 05 2025 06:13:22 PM UTC

Confidence Status Last Update:: 02/Apr/25 5:46 PM