[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:
Duplicate
duplicates SERVER-50938 TenantMigrationAccessBlocker should e... Closed
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 ]

SERVER-50938 made all TenantMigrationAccessBlockers share a single executor.

Generated at Thu Feb 08 05:22:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.