[SERVER-65368] Fix the expected number of deletion batches in change_streams_pre_image_removal_job.js Created: 08/Apr/22 Updated: 29/Oct/23 Resolved: 11/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Denis Grebennicov | Assignee: | Denis Grebennicov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | QE 2022-04-18 | ||||
| Participants: | |||||
| Linked BF Score: | 46 | ||||
| Description |
|
While running the test in `batchedDeletion` "mode", the pre-images are not deleted in doc-by-doc fashion, but rather utilise the efficient multi-deletes functionality. The number of batches is at least equal to two in the test case as we run the one deletion per collection range. However, the `BatchedDeleteStage` may perform deletions in multiple batched depending on for example timing. (it will store the fetched documents in a buffer until the  underlying stage EOFs or a timeout is hit, then the deletion is performed) This is why the number of batches may vary and needs to be accounted in the test. |
| Comments |
| Comment by Githook User [ 11/Apr/22 ] |
|
Author: {'name': 'Denis Grebennicov', 'email': 'denis.grebennicov@mongodb.com', 'username': 'denis631'}Message: |