[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:
Related
is related to SERVER-66057 tenantMigrationDonors and tenantMigra... Closed
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: SERVER-65337 set minThreads to 0: TenantMigrationDonorService, TenantMigrationRecipientService, ShardSplitDonorService.
Branch: master
https://github.com/mongodb/mongo/commit/3a3b70ef88332a8989d4385c14131a840f82eee9

Generated at Thu Feb 08 06:02:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.