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

ShardRegistry should properly handle "possible" RSM updates for the config shard

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • ALL
    • Sharding 2020-10-05, Sharding 2020-10-19
    • 24

      As a result of the way that the ShardRegistry stores/handles the config shard separately from the actual shards, the logic introduced in SERVER-51103 contained a subtle bug, where connection string updates from the RSM for the config shard were not being handled properly. This meant that the ShardRegistry continued to blindly treat "possible" config server connection string updates the same as "confirmed" ones, ie. SERVER-51103 didn't actually fix the problem for the config shard, only for actual shards. This needs to be fixed, since the failures that SERVER-51103 was addressing can happen when interacting with any shard, including the config shard.

            kevin.pulo@mongodb.com Kevin Pulo
            kevin.pulo@mongodb.com Kevin Pulo
            0 Vote for this issue
            2 Start watching this issue