[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: |
|
||||||||
| 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. |