[SERVER-24471] High Memory Utilization by Mongo DB Server Created: 08/Jun/16 Updated: 14/Jul/16 Resolved: 08/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Critical - P2 |
| Reporter: | Rajkumar Kalaiselvam | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We have a Mongo Replica Set of 1 Primary, 3 secondary & 1 Arbiter server. During the recent times, we could see high memory utilization (95 to 99%) in all members of replica set (except Arbiter). On analysis, all we could see is an increase in number of mongo queries which are taking more than 100ms. insert <db name>.system.indexes keyUpdates:0 locks(micros) w:55 XXXms Could you please check and let us know what could be the trigger behind this particular query ? We did check with our application developers and they did confirm that it isn't from the application. Thanks. |
| Comments |
| Comment by Ramon Fernandez Marina [ 08/Jun/16 ] |
|
rajkumar.kalaiselvam@cognizant.com, MongoDB 2.2 is end-of-life and unsupported at this stage, so I'd encourage you to upgrade to a more recent version. MongoDB 3.2.7 is the latest stable version at the time of this writing. Please also 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, |