[SERVER-60419] Make CleanUpForMigrateIn deterministic Created: 04/Oct/21  Updated: 29/Oct/23  Resolved: 06/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.4.9
Fix Version/s: 4.4.10

Type: Bug Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
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: Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
Participants:
Linked BF Score: 58

 Description   

The unit test CleanUpForMigrateIn checks theĀ number of ranges to clean after waiting for the future returned by beginReceive to finish. However, the range is only removed after an asynchronous callback is completed. This creates a race condition in this test between the assertion that there are no ranges to clean and the deletion of the range deletion task from the list.

The test is not actually using the assertions causing the problem, so the solution is simply to remove them.



 Comments   
Comment by Githook User [ 06/Oct/21 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-60419 Make CleanUpForMigrateIn deterministic
Branch: v4.4
https://github.com/mongodb/mongo/commit/aeb7d315a3e9c8a86dc005cee34a1cc1867b10c8

Generated at Thu Feb 08 05:49:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.