[SERVER-70934] batched_multi_deletes_large_transaction.js fails on slow machines due to unexpected batching behavior Created: 28/Oct/22  Updated: 29/Oct/23  Resolved: 28/Oct/22

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2022-11-14
Participants:
Linked BF Score: 149

 Description   

On slow machines, batched_multi_deletes_large_transaction.js occasionally fails because the delete operation removes a subset of the documents in the collection rather than fail outright with a TransactionTooLarge error. This is because the batched delete stage may break up the overall delete request into multiple batches to avoid exceeding the threshold set in batchedDeletesTargetBatchTimeMS. This setting is intended to avoid having each batch of deletes generated by the delete stage take too long to execute on both the primary and secondary nodes.

For the purposes of this test, we would like to have the batched query stage batch all the delete operations in a single batch. Therefore, we should set batchedDeletesTargetBatchTimeMS threshold to be unlimited by making it zero per IDL documentation.



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

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-70934 batched_multi_deletes_large_transaction.js disables batched query time limit
Branch: master
https://github.com/mongodb/mongo/commit/dddf34c61c2cab85bb3434df4fae2be5f244e51d

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