[SERVER-28399] "Shard not found for server" error when mongos does not use alphanumerical order of hosts in its connect string Created: 20/Mar/17  Updated: 06/Dec/22  Resolved: 28/Mar/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.2.12, 3.4.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-22485 ShardNotFound error when looking up r... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

The command execution path uses dbclient_rs and this in turn results in looking up ShardRegistry _lookup map with the connection string returned from ResplicaSetMonitor::getConfirmedServerAddress method that returns the string created form the std::set of node addresses.
This happens only in the command path. i.e the find() will work but the count() will not as its converted to a command by mongo shell.


Generated at Thu Feb 08 04:18:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.