[SERVER-75849] updateReplicaSetOnConfigServer should not skip config server Created: 07/Apr/23  Updated: 29/Oct/23  Resolved: 10/Apr/23

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding NYC 2023-04-17
Participants:

 Description   

When a shard's configuration changes, each mongos will detect this and then update the corresponding config.shards document in the config server. Currently, this logic skips the update if the replica set that changed was the config server, but now the config server can be a shard, so we should not skip this step.



 Comments   
Comment by Githook User [ 10/Apr/23 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-75849 updateReplicaSetOnConfigServer should not skip config server
Branch: master
https://github.com/mongodb/mongo/commit/a37946ca13ae1d1bab79b8e47fd9d70d2ee0cf27

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