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

verify that shardVersion not sent on any commands sent from mongos to a shard before shard is sharding aware

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2016-08-29, Sharding 2016-09-19

    Description

      Example:

      3.2 mongos adds 3.4 --shardsvr mongod.

      The shardIdentity is inserted asynchronously on the mongod through the config.

      The mongos immediately starts using the new shard, though the shard may not have received its shardIdentity (and thus enabled its sharding state) yet.

      Make sure any commands that the mongos can send before a command that performs setShardVersion (moveChunk, splitChunk, etc) do not include shardVersion info. If they do, the mongod will massert:

      https://github.com/mongodb/mongo/blob/9a1688ba6c07117405c46cc6fb1275cb1fcbb4cf/src/mongo/db/commands/dbcommands.cpp#L1377-L1391

      Attachments

        Activity

          People

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: