[SERVER-51257] ShardRegistry should properly handle "possible" RSM updates for the config shard Created: 01/Oct/20  Updated: 29/Oct/23  Resolved: 04/Oct/20

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

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

Issue Links:
Depends
Problem/Incident
is caused by SERVER-51103 RSM calls updateReplSetHosts() with p... Closed
Related
related to SERVER-51230 jstests which use shardingStatus's co... Closed
is related to SERVER-51341 Unittest ShardRegistry handling of up... Backlog
is related to SERVER-51342 ShardRegistry should forget connectio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-10-05, Sharding 2020-10-19
Participants:
Linked BF Score: 24

 Description   

As a result of the way that the ShardRegistry stores/handles the config shard separately from the actual shards, the logic introduced in SERVER-51103 contained a subtle bug, where connection string updates from the RSM for the config shard were not being handled properly. This meant that the ShardRegistry continued to blindly treat "possible" config server connection string updates the same as "confirmed" ones, ie. SERVER-51103 didn't actually fix the problem for the config shard, only for actual shards. This needs to be fixed, since the failures that SERVER-51103 was addressing can happen when interacting with any shard, including the config shard.



 Comments   
Comment by Githook User [ 04/Oct/20 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-51257 ShardRegistry should properly handle "possible" RSM updates for the config shard
Branch: master
https://github.com/mongodb/mongo/commit/9cc6fab62d3c66d5ed3517271f6e0fdfa62cd27b

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