[SERVER-6680] Replica seed list in the config servers can be left outdated Created: 01/Aug/12  Updated: 06/Dec/22  Resolved: 21/Mar/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.2.0-rc0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6605 How to add a replica set's member int... Closed
Related
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

We never check whether ConfigServer::replicaSetChange was able to successfully update the shard list with the newly updated seed list and this could leave the seed list in config servers to be outdated for a long time since this only gets triggered once ReplicaSetMonitor sees that the local replica set host list it has is different from isMaster.



 Comments   
Comment by Gregory McKeon (Inactive) [ 21/Mar/18 ]

We refactored the RSM significantly since this ticket was filed.

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