[SERVER-68799] Fix recipient service access blocker logic for shard merge Created: 12/Aug/22 Updated: 27/Oct/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christopher Caplinger | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | shard-merge-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Serverless
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Server Serverless 2022-08-22 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
on L2729-L2731, we call getTenantMigrationRecipientAccessBlocker with stateDoc.getTenantId(). For shard merge, tenant id here will be empty. as such we are not actually cleaning up the access blocker from the previous migration attempt. |
| Comments |
| Comment by Suganthi Mani [ 03/Mar/23 ] |
|
After, |
| Comment by Suganthi Mani [ 29/Aug/22 ] |
|
christopher.caplinger@mongodb.com Please wait until milestone3 design gets approved for this ticket. |