[SERVER-60738] Update metadata manager tests for non-existing collections Created: 15/Oct/21 Updated: 29/Oct/23 Resolved: 20/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.4.10 |
| Fix Version/s: | 4.4.11 |
| Type: | Improvement | 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: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding EMEA 2021-10-18, Sharding EMEA 2021-11-01 | ||||
| Participants: | |||||
| Linked BF Score: | 56 | ||||
| Description |
|
There are multiple race conditions that have been introduced by the changes made to the range deletion utils which are causing race conditions and failures in the metadata manager unit tests. This ticket is to think through the tests and update them instead of having to address each one as it eventually fails. |
| Comments |
| Comment by Githook User [ 19/Oct/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |