Details
-
Task
-
Resolution: Done
-
Critical - P2
-
None
-
None
-
None
-
None
Description
If a mongos tries to connect with a different config string (for example if hostnames changed from local to fully qualified names) an exception will be logged showing the old & new configuration string and " mongos specified a different config database string ":
Tue Feb 19 17:19:37 [conn1] warning: db exception when initializing on config:mongo-c1.sample.corp:27017,mongo-c2.sample.corp:27017,mongo-c3.sample.corp:27017, current connection state is { state: { conn: "", vinfo: "config:mongo-c1.sample.corp:27017,mongo-c2.sample.corp:27017,mongo-c3.sample.corp:27017", cursor: "(none)", count: 0, done: false }, retryNext: false, init: false, finish: false, errored: false } :: caused by :: 15907 could not initialize sharding on connection data/p1.sample.corp:27017,p2.sample.corp:27017,p3.sample.corp:27017,p4.sample.corp:27017 :: caused by :: mongos specified a different config database string : stored : mongo-c1:27017,mongo-c2:27017,mongo-c3:27017 vs given : mongo-c1.sample.corp:27017,mongo-c2.sample.corp:27017,mongo-c3.sample.corp:27017
|
This can be resolved either by restarting with the correct (old) config string or by restarting mongos/mongods to reflect the new config string.