[SERVER-65337] Tenant migration, split, and merge POS's should default their thread pools to 0 threads Created: 07/Apr/22 Updated: 29/Oct/23 Resolved: 31/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Adi Agrawal |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Server Serverless 2022-09-05 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently the TenantMigrationDonorService's thread pool uses the ThreadPool::Limits::minThreads default, which is 1. It should instead set the minThreads to 0, similar to how it sets maxThreads to repl::maxTenantMigrationDonorServiceThreadPoolSize. We should update TenantMigrationDonorService, as well as check and update TenantMigrationRecipientService and the split service if needed. |
| Comments |
| Comment by Githook User [ 31/Aug/22 ] |
|
Author: {'name': 'Adityavardhan Agrawal', 'email': 'aa729@cornell.edu', 'username': 'Adityav369'}Message: |