-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 1.8.0
-
Component/s: Sharding
-
None
-
Environment:Linux 64Bit
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When starting a routing server and a config server is not online at that moment, instead of connecting later, an exception is thrown and the routing server exits immediatly
Fri Apr 1 14:12:44 reconnect mongo-int1:9999 failed couldn't connect to server mongo-int1:9999
Fri Apr 1 14:12:44 query failed to: mongo-int1:9999 exception
Fri Apr 1 14:12:44 query failed to: mongo-int1:9999 exception
Fri Apr 1 14:12:44 query failed to: mongo-int1:9999 exception
Fri Apr 1 14:12:44 query failed to: mongo-int1:9999 exception
Fri Apr 1 14:12:44 trying reconnect to mongo-int3:9999
Fri Apr 1 14:12:44 reconnect mongo-int3:9999 failed couldn't connect to server mongo-int3:9999
Fri Apr 1 14:12:44 ~ScopedDbConnection: _conn != null
uncaught exception in mongos main:
8003 SyncClusterConnection::insert prepare failed: 9001 socket exception [5] mongo-int1:9999:{}9001 socket exception [6] mongo-int3:9999:{}
This should not happen as http://jira.mongodb.org/browse/SERVER-1936 is marked as fixed