Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
Description
These errors are not generated by the mongos instance and, therefore, will not appear in mongos log files.
Why are mongoses singled out when this affects mongods as well?
compares the number of open file descriptors and connections to the maximum connections limit
It does not look at the number of file descriptors, only the number of connections. This is trying (and failing) to say that the "max open fds" ulimit is what determines the "available" connections as reported by the server.
In ping documents
Pings have nothing to do with it, apart from being where a user can find the evidence if they want. This should just talk about serverStatus, since that's where the information comes from.
its serverStatus.connections values, if the sum of the current value plus the available value
Not clear that "current" and "available" are fields inside the "serverStatus.connections" sub-document.
is less than the maxConns configuration value
It's now net.maxIncomingConnections.
To prevent this error, we recommend you set ulimit open files to 64000. We also recommend setting the maxConns command in the mongo shell to at least the recommended settings.
Remove "at least" — having maxConns which is significantly higher than the ulimits is a great way to cause this message.
These are all in addition to the issues pointed out in MMS-2416 and MMS-2541.