[SERVER-29787] MongoDB allocate and free too much memory Created: 22/Jun/17 Updated: 08/Feb/23 Resolved: 05/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | 아나 하리 | Assignee: | Mark Agarunov |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | 1) Insert 50000000 documents in the test collection. |
| Participants: |
| Description |
|
When few queries process many documents (for example, full collection scan), Take a look at the attached graph. And this case happen very often. I think you can reproduce this case easily. |
| Comments |
| Comment by Mark Agarunov [ 05/Jul/17 ] |
|
Hello matt.lee, Thank you for the response. As this issue cannot currently be reproduced, I've closed this ticket. If this is an issue for you in the future, please let us know and we will reopen the ticket. Thanks, |
| Comment by 아나 하리 [ 30/Jun/17 ] |
|
Hi Mark. I have seen this case in quite a while, so diagnostics data is gone. Thanks. |
| Comment by Mark Agarunov [ 22/Jun/17 ] |
|
Hello matt.lee, Thank you for the report. To better understand what may be causing the memory usage, could you please archive and upload the $dbPath/diagnostic.data directory and attach it to this ticket? This should give us a better idea of what may be using the memory. Thanks, |