[SERVER-7257] mongos log message seems wrong / referring to the wrong shard??? Created: 04/Oct/12  Updated: 11/Jul/16  Resolved: 07/Mar/14

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

Type: Bug Priority: Minor - P4
Reporter: Dwight Merriman Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-5625 New sharded connections to a namespac... Closed
Operating System: ALL
Participants:

 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



 Comments   
Comment by auto [ 04/Oct/12 ]

Author:

{u'date': u'2012-10-04T10:42:53-07:00', u'email': u'dwight@10gen.com', u'name': u'Dwight'}

Message: SERVER-7257 this ticket is manifesting in checkAllVersions(). this change is a small mitigation to just
tell you what shard failed in checkAllVersions. So it doesn't fix the root version but should be
incrementally helpful. The real solution is probably to do some sort of ShardConnectionException or
something where at throw time the shard is known and its identity bundled with the error itself.
Branch: master
https://github.com/mongodb/mongo/commit/aeb1c98985e65919a05e8337dcf61578eba9f52d

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