[SERVER-76858] Disable Serverless machinery if serverless is not enabled Created: 04/May/23 Updated: 29/Oct/23 Resolved: 19/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Didier Nadeau | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Server Serverless 2023-05-15, Server Serverless 2023-05-29, Server Serverless 2023-06-12, Server Serverless 2023-06-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Now that Atlas has started using the `–serverless` parameter, we can use it to decide if we need the serverless machinery at startup. If we don't, not adding it will remove superfluous logs and operations. We can exit early from the MTAB logic (checkIfCanRead, etc), not starting the PrimaryOnlyService and OpObserver for Tenant Migration, Shard Merge and Shard Split. |
| Comments |
| Comment by Githook User [ 16/Jun/23 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |