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

Occasionally getting "Initialized wire specification" when connecting

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.13, 6.0.2, 6.2.0-rc0
    • Affects Version/s: 5.0.3
    • Component/s: None
    • Fully Compatible
    • ALL
    • v6.0, v5.0
    • Hide

      Not reproducible, happens only occasionally.

      Show
      Not reproducible, happens only occasionally.

      I just upgraded my Sharded cluster to version 5.0.3. Sometime when I connect to mongos then I get this information message:

      {
      	"t": {
      		"$date": "2021-10-08T08:02:49.206Z"
      	},
      	"s": "I",
      	"c": "NETWORK",
      	"id": 4915701,
      	"ctx": "-",
      	"msg": "Initialized wire specification",
      	"attr": {
      		"spec": {
      			"incomingExternalClient": {
      				"minWireVersion": 0,
      				"maxWireVersion": 13
      			},
      			"incomingInternalClient": {
      				"minWireVersion": 0,
      				"maxWireVersion": 13
      			},
      			"outgoing": {
      				"minWireVersion": 0,
      				"maxWireVersion": 13
      			},
      			"isInternalClient": false
      		}
      	}
      }
      

      For me this is a problem, because the mongo script runs as automatic job and a non-emtpy return value is considered as an error. Apart from that, it is annoying for the user.

       

      Is the a solution to get rid of this message?

       

            Assignee:
            ryan.egesdahl@mongodb.com Ryan Egesdahl (Inactive)
            Reporter:
            wernfried.domscheit@sunrise.net Wernfried Domscheit
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: