[SERVER-64107] Clean up orphaned doc handling in the batched deleter Created: 02/Mar/22  Updated: 29/Oct/23  Resolved: 26/May/22

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

Type: Task Priority: Major - P3
Reporter: Josef Ahmad 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
depends on SERVER-65859 Enable filtering of change steam even... Closed
depends on SERVER-64972 Generate change stream events for bat... Closed
depends on SERVER-65858 Mark the applyOps entries when the op... Closed
Duplicate
is duplicated by SERVER-64197 Make batched deletes not generate cha... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-04-04, Execution Team 2022-04-18, Execution Team 2022-05-02, Execution Team 2022-05-16, Execution Team 2022-05-30
Participants:

 Description   

Similar to the DeleteStage, do not delete documents that are not owned by the shard in order to avoid generating spurious change stream events.



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

Author:

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

Message: SERVER-64107 Clean up orphan handling in BatchedDeleteStage
Branch: master
https://github.com/mongodb/mongo/commit/2330ce3962a1cbce03510d6cf8ccacc82e637c76

Comment by Josef Ahmad [ 17/May/22 ]

Marking as unblocked as the dependencies are now resolved.

Comment by Josef Ahmad [ 06/May/22 ]

I changed the title of this ticket. The feature has been implemented as part of SERVER-63044, where as a workaround we don't batch "fromMigrate" deletes, and now needs a cleanup once SERVER-65859 is completed.

Comment by Haley Connelly [ 06/Apr/22 ]

Moving out of progress until the plan for SERVER-64972 is established

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