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

Make --shardsvr required for a mongod to be used as a shard

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.12
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • Sharding 18 (08/05/16), Sharding 2016-08-29

      3.4 onwards:

      a shard can become shard aware in two ways:

      • started with --shardsvr and shardIdentity document found on disk
      • started with --shardsvr and receive shardIdentity insert

      so, we will eventually reject all sharding commands if:

      • not started with --shardsvr
      • started with --shardsvr but not yet sharding aware


      for backwards compatibility with 3.2:

      a shard can also become shard aware if:

      • started with --shardsvr and receive command that initializes sharding awareness

      so (what this ticket does):

      reject all sharding commands except a whitelist of commands that initialize sharding awareness.

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            crystal.horn@mongodb.com Crystal Horn
            0 Vote for this issue
            7 Start watching this issue