[SERVER-27102] force a ShardRegistry reload in the beginning of addShard to ensure a removed shard's ReplicaSetMonitor has been detached Created: 17/Nov/16  Updated: 05/Apr/17  Resolved: 18/Nov/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.0-rc3
Fix Version/s: 3.4.1, 3.5.1

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
Backport Completed:
Sprint: Sharding 2016-11-21, Sharding 2016-12-12
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 02/Dec/16 ]

Author:

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

Message: SERVER-27102 force a ShardRegistry reload in the beginning of addShard to ensure a removed shard's ReplicaSetMonitor has been detached
Branch: v3.4
https://github.com/mongodb/mongo/commit/fd354e75945f30e10db3b45bc04f4bc6091362de

Comment by Githook User [ 18/Nov/16 ]

Author:

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

Message: SERVER-27102 force a ShardRegistry reload in the beginning of addShard to ensure a removed shard's ReplicaSetMonitor has been detached
Branch: master
https://github.com/mongodb/mongo/commit/d6029bd26e790f78fe7781a7a26c9b863127e70d

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