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

Audit all uses of ShardRegistry configShard on config server to verify they are safe to use ShardRemote

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding NYC 2023-04-03

    Description

      This project changed getting the config shard from the shard registry on the config server to return a ShardRemote instead of a ShardLocal. This means operations that were previously always process local, may now target other config server nodes. This could be problematic, e.g. if code relies on receiving a replication state change error after a failover, but now will retarget the new primary. We should audit visually and via invariants, etc. that all uses of ShardLocal before SERVER-71891 are safe to use ShardRemote.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: