[SERVER-25133] fix racy conditions in handling addShard from 3.2 mongos Created: 18/Jul/16  Updated: 13/Aug/16  Resolved: 18/Jul/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.11

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 18 (08/05/16)
Participants:
Linked BF Score: 0

 Description   

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


 Comments   
Comment by Githook User [ 18/Jul/16 ]

Author:

{u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}

Message: SERVER-25133 fix racy conditions in handling addShard from 3.2 mongos
Branch: master
https://github.com/mongodb/mongo/commit/ec47d514660aab52d78d57f60e023bab264e37d5

Generated at Thu Feb 08 04:08:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.