-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: 2.1.6
-
Component/s: MongoDB 3.2
-
Environment:Ubuntu (Heroku dyno)
-
Empty show more show less
We've been experiencing periodic outages of a minute or shorter in our mongo connection on a high traffic site. To remedy the situation we upgraded to the latest driver.
We seem to still have issues. The error thrown by the driver is now:
```
0:MongoError: TypeError: Cannot read property 'noRelease' of undefined
1: at null.messageHandler (/app/node_modules/mongodb-core/lib/topologies/server.js:284:29)
2: at TLSSocket.<anonymous> (/app/node_modules/mongodb-core/lib/connection/connection.js:273:22)
3: at emitOne (events.js:77:13)
4: at TLSSocket.emit (events.js:169:7)
5: at TLSSocket.net.Socket.emit (/app/node_modules/net-debug/index.js:18:14)
6: at readableAddChunk (_stream_readable.js:146:16)
7: at TLSSocket.Readable.push (_stream_readable.js:110:10)
8: at TLSWrap.onread (net.js:523:20)
```
The error happens about once an hour (irregular) on a high traffic site doing thousands of mongo requests per minute.
Before we upgraded we were running an older driver that reported "Error querying server".
We've been in contact with our DB provider, and they say nothing is wrong with the mongo instance. (Not sure I trust that 100%).
Do you have any idea what could cause the above error, and how we can debug it further? It seems something is happening, that is not handled that gracefully by the driver.