[SERVER-51043] Remove the TenantMigrationAccessBlocker when the state doc is removed instead of when expireAt is set Created: 18/Sep/20 Updated: 29/Oct/23 Resolved: 21/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.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 | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2020-09-21, Sharding 2020-10-05 |
| Participants: |
| Description |
|
Right now the TenantMigrationAccessBlocker is removed by the OpObserver when the expireAt field is set. This doesn't align with the design. It should be removed when the donor's state document is removed. Also, this is causing an issue if the donor restarts. If expireAt is set prior to shutdown but the TTL does not get to remove the donor's state doc before that, then on restart the TenantMigrationAccessBlocker would get recovered but never removed. |
| Comments |
| Comment by Githook User [ 21/Sep/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}Message: |