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

setFCV on a cluster can fail to call setFCV on shards if the config server primary's ShardRegistry is empty

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.6.0-rc2
    • 3.6.3, 3.7.1
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Sharding 2017-11-13, Sharding 2017-12-04
    • 0

    Description

      It's possible for the previous ShardRegistry reload to have failed (e.g., due to the majority snapshot not being available), and setFCV uses ShardRegistry::getAllShardIds(), which does not force a ShardRegistry reload.

      We could band-aid this by adding a ShardRegistry reload before the ShardRegistry::getAllShardIds(), or we could force a reload inside getAllShardIds() (and maybe also ShardRegistry::getNumShards(), a similar function that has the same issue).

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: