[SERVER-37936] Mongod can't handle more than 32K connectipn Created: 06/Nov/18 Updated: 06/Nov/18 Resolved: 06/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Performance, Replication |
| Affects Version/s: | 3.2 Required |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rizal | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
Mongod can't be access whenever mongod reach > 32K concurrent connections. Each time it reach the number, server can't be access
Mongod Environtment
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 06/Nov/18 ] |
|
Hello Rizal, I recommend checking the various kernel settings within your OS configuration to confirm that everything is set according to our Operations Checklist. Additionally, please note that MongoDB 3.2 has reached its end-of-life so we strongly recommend you upgrading versions when you are able. If you have additional questions on this topic, please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. Because this is not a bug within MongoDB, I will now close this SERVER ticket. Thank you, Danny |