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

Only apply changed connection strings inside ShardRegistry::_lookup()

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.0.0
    • None
    • Sharding
    • None
    • Fully Compatible

    Description

      The code inside ShardRegistry::_lookup() blindly applies the latest connection string for each shard to the ShardRegistryData being generated. Most of the time, these connection strings will be the same as what's already in the ShardRegistryData, meaning that the work of integrating them is unnecessary. It should be possible to short-circuit (continue) prior to this work, if the returnData ShardRegistryData already associates this connection string with the correct shard.

      Attachments

        Activity

          People

            jaume.moragues@mongodb.com Jaume Moragues (Inactive)
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: