[SERVER-50339] [required cleanup] Tenant migration donor code creates a new TaskExecutor for each TenantMigrationAccessBlocker Created: 17/Aug/20 Updated: 06/Dec/22 Resolved: 17/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | pm-1791_milestone-A | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently a new TaskExecutor is created and given to each TenantMigrationAccessBlocker, and the TenantMigrationAccessBlocker only uses it to wait for the commit or abort OpTime to become majority committed. At the very least, all TenantMigrationAccessBlockers should share a single executor, but we should also think about whether we can avoid creating a separate executor just for this. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 17/Sep/20 ] |
|
|