-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.6.11
-
Component/s: Logging
-
Fully Compatible
-
Sharding 2019-10-21
-
(copied to CRM)
When the mongod server responds to the client with something like the following (mongo shell in this example):
MongoDB Enterprise mongos> show dbs 2019-04-08T17:54:08.081+0000 E QUERY [js] Error: listDatabases failed:{ "ok" : 0, "errmsg" : "cannot add session into the cache", "code" : 261, "codeName" : "TooManyLogicalSessions",
a corresponding error is not logged to the mongodb.log for the mongoS, making troubleshooting more difficult if the error from the application side is not immediately available. This seems like a low-hanging-fruit improvement we can make to facilitate troubleshooting.