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.
- is caused by
-
SERVER-51103 RSM calls updateReplSetHosts() with partial connection strings
-
- Closed
-
- is related to
-
SERVER-51341 Unittest ShardRegistry handling of updated connection strings from the RSM
-
- Backlog
-
-
-
- Closed
-
- related to
-
-
- Closed
-