Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-28399

"Shard not found for server" error when mongos does not use alphanumerical order of hosts in its connect string

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.12, 3.4.2
    • Component/s: Sharding
    • None
    • Sharding
    • ALL

      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.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: