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

fix racy conditions in handling addShard from 3.2 mongos

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 18 (08/05/16)
    • 0

      Fixes the following bugs:

      • use kNoWaitWriteConcern for performing the local update to config.shards in the callback for the shardIdentity upsert
      • release the _addShardHandlesMutex before the local update to config.shards
      • use Client::initThreadIfNotAlready instead of Client::initThread and Client::destroy

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

              Created:
              Updated:
              Resolved: