[SERVER-7278] mongos doesn't always update shards in response to replica set changes Created: 05/Oct/12  Updated: 10/Dec/14  Resolved: 07/Mar/14

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

Type: Bug Priority: Major - P3
Reporter: Ben Becker Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: replicaset, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-3333 mongos sometimes does not update conf... Closed
is related to SERVER-4399 mongos doesn't always update shards i... Closed
is related to SERVER-7291 MongoS can hang after replica set rec... Closed
Operating System: ALL
Participants:

 Description   

When running rs.reconfig() to remove a node from a replica set, the config servers do not reflect the updated connection string. That is, config.shards is not updated.



 Comments   
Comment by Greg Studer [ 07/Mar/14 ]

The ReplicaSetMonitor has changed pretty drastically in 2.6, so closing this ticket as Cannot Reproduce.

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