Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-71299

Fail startup if no ClusterId is found

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28

      Config server generates and persists a new ClusterId on first startup and every other node load this Cluster ID from the config server at startup using the ClusterIdentityLoader .

      The problem is that currently in case no config version document is found on the config server at startup the ClusterIdentityLoader will load a fake zero-filled OID.
      This is wrong and can bring to unexpected error when we later try to add a shard.

      Instead we should make ClusterIdentityLoader::loadClusterId() to simply fail if no config version document is found on the config server.

            tommaso.tocci@mongodb.com Tommaso Tocci
            tommaso.tocci@mongodb.com Tommaso Tocci
            0 Vote for this issue
            3 Start watching this issue