[SERVER-57847] RenameRangeDeletionsTest fixture should join the MigrationUtilExecutor on teardown Created: 18/Jun/21 Updated: 29/Oct/23 Resolved: 22/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.1.0, 5.0.0-rc2 |
| Fix Version/s: | 5.0.0-rc3, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Sharding EMEA 2021-06-28 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 150 | ||||||||
| Description |
|
RenameRangeDeletionsTest:;teardown() calls shutdown() on the MigrationUtilExexutor, but it does not join() it to wait for completion. As a result, rangeDeletions may continue as the fixture is being destructed, and attempt to use the CatalogCache after it has been destructed. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 22/Jun/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 22/Jun/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |