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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.12
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2016-08-29, Sharding 2016-09-19

      Description

      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.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: