Fail startup if no ClusterId is found

XMLWordPrintableJSON

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

      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.

              Assignee:
              Tommaso Tocci
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: