[SERVER-64598] FSM workload for the batched deleter Created: 17/Mar/22  Updated: 29/Oct/23  Resolved: 05/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: Yujin Kang Park
Resolution: Fixed Votes: 0
Labels: PM-2227-M3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Participants:

 Description   

Determine whether the existing FSM workloads can cover batch-deleting large ranges of documents concurrently with other write operations, and create/extend as needed.



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

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-64598: Add batched multi deletes FSM workload
Branch: master
https://github.com/mongodb/mongo/commit/8c7cff6c0312cf874947ae8d41578428475ed01b

Comment by Josef Ahmad [ 31/Mar/22 ]

The  remove_where.js workload under the batched delete passthrough exercises a concurrent, independent delete that removes document that were staged for deletion by the batched deleter.

Another interesting workload would consist of an independent update that modifies a document staged for deletion in a way that does not match any longer the query predicate for the deletion. Let's determine if this workload already exists.

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