[SERVER-66141] Donor tenant access blockers persist on recipient before recipient cleanup Created: 03/May/22 Updated: 29/Oct/23 Resolved: 04/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Matt Broadstone |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Server Serverless 2022-05-16 |
| Participants: |
| Description |
|
Tenant access blockers are installed on all donor nodes prior to executing a split operation. These access blockers are eventually removed from the recipient when the recipient primary steps up and deletes the state document. However, it's possible that requests are rerouted to the recipient before it has had a chance to delete the state document, so we should remove the access blockers as soon as we successfully apply the recipient config. |
| Comments |
| Comment by Githook User [ 04/May/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |