[SERVER-71084] RangeDeleterService test util needs to insert range deletion task with pending set Created: 04/Nov/22 Updated: 29/Oct/23 Resolved: 12/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.2
|
||||||||
| Steps To Reproduce: | Add sleep(2) between the task insertion and the update in the range_deleter_service_test_util and running the CSR test |
||||||||
| Sprint: | Sharding EMEA 2022-12-12 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 5 | ||||||||
| Description |
|
In the range_deleter_service_test_util, there is a function to register a task with the range deleter. It registers the task as pending and then unsets the pending flag. However, the pending flag is not set on the task in the collection_sharding_runtime_test, so when the task is inserted, it is not marked as pending. This can lead to the update removing the pending flag failing since the range deletion has already completed and the task has been removed. We need to ensure that the document that is being persisted has the pending flag set before it is unset. |
| Comments |
| Comment by Liubov Molchanova [ 11/Jan/23 ] |
|
Requesting a backport for v6.2 as the issue reproduced in BFG-1744150 |
| Comment by Githook User [ 12/Dec/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |