[SERVER-64083] Add a missing step to create tenant migration access blockers for the shard split service Created: 01/Mar/22 Updated: 29/Oct/23 Resolved: 06/Apr/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: | Mathis Bessa | Assignee: | Mathis Bessa |
| 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-04-18 |
| Participants: |
| Description |
|
When a node is restarted / recovered, shard split donor service needs to include in it recovery procedure to create any tenant access blocker that might not be created when the current local state doc is not `kUninitialized` The code forĀ recoverTenantMigrationAccessBlockers shows how a node should create access blockers for tenant migration and we should re-use that logic for the shard split donor service. |
| Comments |
| Comment by Githook User [ 06/Apr/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |