[SERVER-66057] tenantMigrationDonors and tenantMigrationRecipients collections created unconditionally at startup Created: 28/Apr/22 Updated: 27/Oct/23 Resolved: 04/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Backlog - Service Architecture |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Didier Nadeau [ 04/Oct/23 ] |
|
The serverless primary only services are now created only in serverless mode. |