[SERVER-65540] Build range deleter service Created: 13/Apr/22  Updated: 06/Dec/22  Resolved: 29/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-65535 Ensure consistent orphaned documents ... Open
is depended on by SERVER-65538 Serialize scheduling of new range del... Closed
Duplicate
Assigned Teams:
Sharding EMEA
Participants:

 Description   

The range-deleter executor serves its purpose of ensuring that orphaned documents get eventually deleted but is not suited for more complex use cases given the "fire and forget" way to schedule tasks and the interconnection with metadata managers .

Purpose of this ticket is to implement a RangeDeleterService that should at least fulfill the following requirements:

  • Being initialized/stopped on step-up/step-down
  • Keeping track of a list of ranges to be deleted and have a thread consuming it (rather than scheduling plenty of tasks on a mono-threaded executor)
  • Keep track of orphaned ranges with ongoing queries, not ready to be deleted (rather than having metadata managers tracking it separately)


 Comments   
Comment by Pierlauro Sciarelli [ 29/Jun/22 ]

Closing the issue as duplicate because a whole project (PM-2849) has been spawned to build a range deleter service

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