-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: MongoDB 3.4
-
Environment:RHEL 7.3, Docker 17.05
-
Empty show more show less
The mongod logging level for network is set to a verbosity of 5.
Both mongos and mongo replicasets are logging the following error in their mongod logs:
2018-04-27T15:00:46.860+0000 D NETWORK [conn64258584] SocketException: remote: x.x.x.x:51774 error: 9001 socket exception [RECV_ERROR] server [x.x.x.x:51774]
These exceptions are incoming from both inter-mongo communication between nodes, and from communication with the client nodejs drivers.
We've already looked at:
https://jira.mongodb.org/browse/NODE-982
The configuration mentioned in that issue:
{ poolSize: 20, socketTimeoutMS: 480000, keepAlive: 300000, ssl: true, sslValidate: false }
- backported by
-
NODE-982 Won't reconnect after "MongoError: Topology was destroyed"
- Closed
-
NODE-1013 SocketException handling request, closing client connection: 9001 socket exception [SEND_ERROR]
- Closed
-
SERVER-20125 ReplicaSet Cluster log lots of "9001 SocketException"
- Closed