[SERVER-35426] MongoDB clocking Created: 05/Jun/18 Updated: 28/Jun/18 Resolved: 06/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | kishore | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
we are using mongo 3.0.3, when we see mongo connections goes beyond 1700 then the databases becomes unresponsive until the number of connections comes down to 1000 or below. the whole process taking more than 30 min. how can we avoid this clocking ?
what parameters need to checked at the time of high connections. when we checked the db.currentOp() - the result is empty but if we check db.currentOp(true) it shows more than 1500 idle connections. |
| Comments |
| Comment by Ramon Fernandez Marina [ 06/Jun/18 ] |
|
Thanks for your report. MongoDB 3.0 is EOL, please upgrade to a supported version (3.6.5 at the time of this writing, and a 4.0.0-rc1 release candidate is also available for testing) at your earliest convenience. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Regards, |