Handle config server UUID in shard registry initialization

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-07-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a TODO in the codebase referencing a resolved ticket which is assigned to you.

      Please follow this link to see the lines of code referencing this resolved ticket:
      https://github.com/10gen/mongo/search?q=SERVER-127407&type=Code

      The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this ticket to represent the work you're actually doing.


      Adding some more context here - when initializing the config shard in the shard registry, we don't necessarily know the config server's UUID (if we are on a shard, we only know the connection string and if we are on a config server secondary we haven't necessarily seen the shard identity yet). In this ticket, we need to decide how we want to handle this case.

      It seems likely that having the config shard data in the shard registry missing the UUID would be okay in the vast majority of cases, the only question is whether someone (especially on the config server) would expect this to be initialized at some point in the future.

            Assignee:
            Allison Easton
            Reporter:
            xgen-buildbaron-user
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: