[SERVER-75509] Range deleter must locally drop drained collections Created: 30/Mar/23  Updated: 12/Sep/23  Resolved: 12/Sep/23

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

Type: Improvement Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Won't Do Votes: 0
Labels: range-deleter-improvements
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18
Participants:
Linked BF Score: 3

 Description   

When all the chunks for a collection have been moved off AND all ongoing reads on orphaned documents have drained, the range-deleter should safely be able to:

  • Stop incoming migrations for the collection
  • Drop the collection locally

This would help avoid all the unnecessary overhead caused by the range deleter: delete the whole collection/indexes rather than doing it document by document.



 Comments   
Comment by Pierlauro Sciarelli [ 12/Sep/23 ]

Closing the ticket as won't do because SERVER-77359 will give the ability to turn off/on the range deleter dynamically so users will be able to stop range deletions on draining shards.

Additionally, in new versions resharding will be used on add/remove shard hence no orphans will be generated.

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