[SERVER-66210] BatchedDeleteStage doesn't indicate when completion is caused by pass targets Created: 04/May/22  Updated: 29/Oct/23  Resolved: 09/May/22

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

Type: Improvement Priority: Major - P3
Reporter: Haley Connelly Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: PM-2227-M3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-56194 Make TTL deletes fair Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-05-16
Participants:

 Description   

A BatchedDeleteStage can return PlanStage::IS_EOF in two different scenarios
(1) the child returned IS_EOF, there is nothing left to fetch, and the buffer has been drained
(2) a pass target was met, and even if there are more documents to fetch from the child, the pass is doneĀ 

For batched deletes that specify pass targets, such as the TTLMonitor, it is useful to differentiate between the two scenarios to know if the command should be executed again



 Comments   
Comment by Githook User [ 09/May/22 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-66210 Indicate when pass targets cause BatchedDeleteStage completion
Branch: master
https://github.com/mongodb/mongo/commit/cd9c111f2707f7e641765e9c00c1cb036df61c9f

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