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.