[SERVER-63975] initial sync fails while tenant donor access blocking is in effect Created: 24/Feb/22 Updated: 29/Oct/23 Resolved: 25/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Hugh Tong (Inactive) |
| 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-03-07, Server Serverless 2022-03-21, Server Serverless 2022-04-04 |
| Participants: |
| Description |
|
If you try to initial sync a node into a cluster that has active tenant blocking for tenant migrations as a donor, the initial sync will fail because it will try to read the blocked tenant's data. We can correct this problem with a solution similar to |
| Comments |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Hugh Tong', 'email': 'hugh.tong@mongodb.com', 'username': 'cortrain'}Message: |