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

mongos log message seems wrong / referring to the wrong shard???

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      on first query of opening a mongo shell and querying a sharded collection where shard 2 of 2 is down it gives me an error regarding reachability of shard 1. after first query it is shard 2 in the log. very weird. You'll see the log line talks about both shard 1 and shard 2 hosts (shard 2, a non-replica set at dm_hp:27001, is what is truly down in the example).

      Thu Oct 04 13:10:52 [conn8] warning: socket exception when initializing on s0:s0/dm_hp:27000,dm_hp:27018, current connection state
       is { state: { conn: "", vinfo: "test.foo @ 2|1||5069e229110d001accf5bb15", cursor: "(none)", count: 0, done: false }, retryNext:
      false, init: false, finish: false, errored: false } :: caused by :: 11002 socket exception [6] server [dm_hp:27001] mongos shardco
      nnection connectionpool error: couldn't connect to server dm_hp:27001
      Thu Oct 04 13:10:52 [conn8] DBException in process: socket exception [CONNECT_ERROR] for dm_hp:27001

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: