[SERVER-26793] in ShardRegistry::reload(), only attempt to remove ReplicaSetMonitor for removed shard if shard was replica set Created: 26/Oct/16  Updated: 31/Oct/16  Resolved: 27/Oct/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.0-rc1
Fix Version/s: 3.4.0-rc2

Type: Improvement 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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-10-31
Participants:

 Description   

A minor fix related to SERVER-26787.



 Comments   
Comment by Githook User [ 27/Oct/16 ]

Author:

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

Message: Revert "SERVER-26793 in ShardRegistry::reload(), only attempt to remove ReplicaSetMonitor for removed shard if shard was replica set"

This reverts commit d01e6cfd8d19290d64040d3acde718a84822e7c6.

ReplicaSetMonitor::remove() also cleans the connections for the host from the global DBConnectionPool, which needs to happen for standalone shards as well as replica set shards.
Branch: master
https://github.com/mongodb/mongo/commit/baad67a57499449338330d68a79efe42e503107b

Comment by Githook User [ 27/Oct/16 ]

Author:

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

Message: SERVER-26793 in ShardRegistry::reload(), only attempt to remove ReplicaSetMonitor for removed shard if shard was replica set
Branch: master
https://github.com/mongodb/mongo/commit/d01e6cfd8d19290d64040d3acde718a84822e7c6

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