[SERVER-53442] Missing topOfOplog in mock donor set in RecipientForgetMigration_WaitUntilStateDocInitialized Created: 18/Dec/20 Updated: 29/Oct/23 Resolved: 18/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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 | ||||
| Sprint: | Repl 2020-12-28 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In TenantMigrationRecipientServiceTest, we use insertTopOfOplog to add oplog entries to the mock replica set so that _getStartOpTimesFromDonor can get the startFetchingOptime in unittests. In unittest RecipientForgetMigration_WaitUntilStateDocInitialized, we are missing such step and so sometimes it would hit this uassert that the unittest doesn't expect if the interrupt from onReceiveRecipientForgetMigration comes after the instance runs _getStartOpTimesFromDonor. To fix this, use insertTopOfOplog to insert a dummy oplog into the mock replica set like other tests do. |
| Comments |
| Comment by Githook User [ 18/Dec/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |