[SERVER-46078] sudden spike in connections for mongos Created: 11/Feb/20 Updated: 13/Feb/20 Resolved: 13/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | sudheer reddy bholla | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
mongodb version used : 3.4.10 instance type : t2.medium (2 cpu,4 gb ram) present parameter settings : I think the issue is related to ticket(https://jira.mongodb.org/browse/SERVER-25027) but as per the documentation for version 3.4 the parameter taskExecutorPoolSize should have values from 4-64 ,I am confused as we have this parameter set to 0 what does value 0 for taskExecutorPoolSize parameter mean in version 3.4
|
| Comments |
| Comment by Carl Champain (Inactive) [ 13/Feb/20 ] |
|
Hi sudheer.bholla@practicefusion.com, MongoDB 3.4 is already end-of-lifed, which means it is unsupported by us. We strongly recommend you upgrade to a supported version. That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. Kind regards, |