Disable Serverless machinery if serverless is not enabled

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Server Serverless 2023-05-15, Server Serverless 2023-05-29, Server Serverless 2023-06-12, Server Serverless 2023-06-26
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Didier Nadeau
              Reporter:
              Didier Nadeau
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: