-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Service Arch
-
ALL
The collections config.tenantMigrationDonors and config.tenantMigrationRecipients are created unconditionally at startup, leading to log messages about their creation in new replica sets. We also log the startup of a primary-only-service for tenant migrations, even though we are not in an context where tenant migration is possible. We should not start up services we aren't using, and we certainly shouldn't log about it.
- is related to
-
SERVER-66058 ShardSplitDonorService starts up even outside of serverless environments
- Closed
- related to
-
SERVER-65337 Tenant migration, split, and merge POS's should default their thread pools to 0 threads
- Closed