[SERVER-70116] Support adding TenantMigrationAccessBlocker for list of tenants Created: 29/Sep/22 Updated: 29/Oct/23 Resolved: 19/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | 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 |
| Sprint: | Server Serverless 2022-10-03, Server Serverless 2022-10-31 |
| Participants: |
| Description |
|
We currently create one access blocker for each tenant being split in a shard split operation, resulting in verbose (and sometimes confusing) log output. This ticket will cover refactoring the TenantMigrationAccessBlockerRegistry to support adding a single access blocker for a list of tenants, and to rework the ShardSplitDonorService's usage of that registry to use methods which use migrationIds. |
| Comments |
| Comment by Githook User [ 19/Oct/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |