[SERVER-42100] MongoDB using high memory and cache Created: 08/Jul/19 Updated: 07/Apr/23 Resolved: 08/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance, WiredTiger |
| Affects Version/s: | 3.2.11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pratiksha Aggarwal | Assignee: | Dmitry Agranat |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
MongoDB memory utilization increases upto 92% and cache usage is also more than 80%. The database stats are as below: db.stats(1024) { "db" : <"CONFIDENTIAL">, "collections" : 555, "objects" : 20797991, "avgObjSize" : 1123.3038404045853, "dataSize" : 22814905.432617188, "storageSize" : 9519780, "numExtents" : 0, "indexes" : 2612, "indexSize" : 2280272, "ok" : 1} |
| Comments |
| Comment by monika yadav [ 12/Jul/19 ] |
|
@dmitry Agranat: It will take some time to upgrade to the latest version. We are running the mongodb on production and it would be very helpful if you can assist us on finding the root cause and the solution. |
| Comment by Dmitry Agranat [ 08/Jul/19 ] |
|
Hi pragupta, MongoDB 3.2 has reached end of life on September 2018. If you encounter this issue after upgrading to the latest MongoDB version (as of today, the latest is 4.0.10), please open a new ticket and we will be happy to investigate. Thank you, |