[SERVER-67739] tenant_migration_donor_retry.js state docs can be cleaned up prior to assertions against them Created: 01/Jul/22 Updated: 29/Oct/23 Resolved: 11/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.3, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christopher Caplinger | Assignee: | Christopher Caplinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Sprint: | Server Serverless 2022-07-11, Server Serverless 2022-07-25 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 35 | ||||||||
| Description |
|
runMigration defaults automaticForgetMigration to true, so it is possible that by the time we (manually) call recipientForgetMigration, the state doc could have already been cleaned up. we should disable automaticForgetMigration and explicitly call recipientForgetMigration to make it more obvious what the test is doing. likewise, tests in this file also mark state docs as garbage collectable and then run queries for said state docs, which means we can run into race conditions if the doc is cleaned up before we query it. |
| Comments |
| Comment by Githook User [ 06/Oct/22 ] |
|
Author: {'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}Message: |
| Comment by Githook User [ 11/Jul/22 ] |
|
Author: {'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}Message: |