[SERVER-60552] Separate test for non-existing collection in metadata_manager_test Created: 08/Oct/21  Updated: 29/Oct/23  Resolved: 11/Oct/21

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

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-18
Participants:
Linked BF Score: 70

 Description   

The fix inĀ SERVER-60419 made the race condition in CleanUpForMigrateIn less likely, but did not eliminate it. There is still a chance, currently, that the deletion of the existing range deletion for the non-existing collection will not happen before the assertions on how many range deletions are still active. Since these tests do not depend on each other, we can simply separate them into two tests and prevent this issue.



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

Author:

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

Message: SERVER-60552 Separate test for non-existing collection in metadata_manager_test
Branch: v4.4
https://github.com/mongodb/mongo/commit/4aee6e6977d61ceebfdc9f8144e2840d0fab4e40

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