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

Ignore fixed dbVersions in ScopedSetShardRole

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding NYC 2023-02-06

    Description

      ScopedSetShardRole will take a dbVersion for the database being accessed while its in scope, and install it on the OperationShardingState of its given opCtx. If the dbVersion is "fixed," it should be ignored since fixed versions are only used for the config and admin databases, which don't have real database metadata, since they must always be owned by the config server. Ignoring these versions matches how remote commands won't include a fixed dbVersion. This can be hit when a config server is acting as a shard when a shard component tries to read from a config db collection.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: