[DOCS-7535] Cloud Manager "Host has low open file limits" page is extremely confusing Created: 30/Mar/16 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 46 weeks ago | ||||
| Epic Link: | docs-troubleshooting | ||||
| Description |
Why are mongoses singled out when this affects mongods as well?
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.
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.
Not clear that "current" and "available" are fields inside the "serverStatus.connections" sub-document.
It's now net.maxIncomingConnections.
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. |