[SERVER-50617] Make TenantMigrationAccessBlocker::abort not invariant that the migration is in blocking state Created: 28/Aug/20 Updated: 29/Oct/23 Resolved: 28/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-A | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2020-09-07 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
Currently, TenantMigrationAccessBlocker::abort has an invariant that the migration must have started blocking reads and writes when the migration aborts. That invariant should be removed because the migration could abort in any state. It could abort if it couldn’t find the recipient host when sending the first recipientSyncData so that case _access would kAllow. |
| Comments |
| Comment by Githook User [ 28/Aug/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}Message: |