[SERVER-59525] TenantMigrationRecipientAccessBlocker isn't being initialized correctly on recovery Created: 24/Aug/21 Updated: 29/Oct/23 Resolved: 13/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Vishnu Kaushik |
| 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: |
v5.0
|
||||||||||||
| Sprint: | Repl 2021-09-20 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 62 | ||||||||||||
| Description |
|
When we reconstruct all access blockers, such as in the case of rollback, we are not initializing the TenantMigrationRecipientAccessBlocker to its correct state depending on whether _rejectBeforeTimestamp exists in the migration document. For example, when the migration is in the kDone state (migration has completed and been forgotten), we are not setting the TenantMigrationRecipientAccessBlocker to the kRejectBefore state even though the _rejectBeforeTimestamp exists. |
| 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 [ 29/Sep/21 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |
| Comment by Githook User [ 13/Sep/21 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |