[SERVER-45053] Possible memory leak when write are large Created: 11/Dec/19 Updated: 24/Aug/23 Resolved: 24/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | demonYang | Assignee: | Dmitry Agranat |
| Resolution: | Declined | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
I have a cluster with 9 shards ,each shard write QPS is 5k/s,the WT cacheSize is configured with 16GB。Mongod emory usage will keep growing over time,eventually leads to mongod OOM. By serverStatus,found that wiredTiger stats reports only 13GB of cache used, but according to ps mongod is using more than 20GB or more When a mongod restarted(killed by OOM),get the mongod process status.
I can collect more information if needed.
wiredTiger cache:
I restarted mongod with --setParameter heapProfilingEnabled=true, after a couple days got a heap-profile result,see details heap-profile-mongod.out |
| Comments |
| Comment by Dmitry Agranat [ 12/Dec/19 ] |
|
demon, I appreciate that going through an upgrade of 4 major versions (3.2- I will go ahead and close this ticket but don't hesitate to reach out once you are on a supported MongoDB version. Regards, |
| Comment by demonYang [ 11/Dec/19 ] |
|
dmitry.agranat |
| Comment by Dmitry Agranat [ 11/Dec/19 ] |
|
MongoDB 3.2 is EOL since September 2018, if you'd like us to take a look at any potential issue, please upgrade to the latest (as of today MongoDB 4.2. Thanks, |