[SERVER-68354] Set `whenToClean` to `now` when marking range deletion task as processing Created: 27/Jul/22  Updated: 29/Oct/23  Resolved: 28/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.1, 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: Sharding EMEA 2022-08-08
Participants:

 Description   

A range deletion task is marked as processing right before the range-deleter starts deleting documents from it. When it gets labeled as such, it also indirectly means that the timeout before triggering the cleanup had been honored.

Given that on step-up the whenToClean field is used to decide when to schedule a task, it makes no sense to delay the scheduling of a task marked as processing since it is ensured that the timeout had been already respected.

Purpose of this ticket is to enhance this update in order to also change the whenToClean field to now.



 Comments   
Comment by Githook User [ 28/Jul/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-68354 Set `whenToClean` to `now` when marking range deletion task as processing
Branch: master
https://github.com/mongodb/mongo/commit/0b02969388ada47ec5b088e9c6a028054a99bf41

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