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

Config server can send wrong cluster ID to shards during addShard if cluster ID ever rolls back

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.12
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • ALL
    • Sharding 2016-08-29, Sharding 2016-09-19

      The first time a config server becomes primary it builds the necessary indexes on the config database and initializes the config.version collection, which includes the cluster ID. It then immediately loads the cluster ID into memory. If the config.version document rolls back, however, we don't clear the cached in-memory cluster ID, so when a new config.version document is written, with a new cluster ID, we won't ever realize that its changed. This means that when we add a shard, we'll provide it the wrong clusterID in its shardIdentity document.

            spencer@mongodb.com Spencer Brody (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            0 Vote for this issue
            2 Start watching this issue