[SERVER-30603] mongos shouldn't log the warning in the log when config server order isn't matching the configuration Created: 10/Aug/17  Updated: 27/Oct/23  Resolved: 11/Sep/17

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

Type: Improvement Priority: Minor - P4
Reporter: Andrey Brindeyev Assignee: Kaloian Manassiev
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-22485 ShardNotFound error when looking up r... Closed
Sprint: Sharding 2017-10-02
Participants:

 Description   

Currently, if the config server's order in the mongos configuration doesn't match the configuration, the following warning message is logged:

W NETWORK  [connXYZ] db exception when initializing on config, current connection state is { state: { conn: "CSRS_ReplicaSet/host1:port1,host2:port2,host3:port3", vinfo: "config:CSRS_ReplicaSet/host3:port3,host1:port1,host2:port2", cursor: "(empty)", count: 0, done: false }, retryNext: false, init: false, finish: false, errored: false } :: caused by :: 70 Shard not found for server: CSRS_ReplicaSet/host1:port1,host2:port2,host3:port3

Since the order of config servers insn't important for CSRS, the warning shouldn't be logged.



 Comments   
Comment by Kaloian Manassiev [ 11/Sep/17 ]

Unfortunately, this warning is in place because of SERVER-22485 which is quite difficult to fix in the 3.2/3.4 and 3.6 code base. We put it there in order to make it easier for users and support to figure out that SERVER-22485 is happening.

Generated at Thu Feb 08 04:24:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.