Details
-
Task
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
Storage Execution
Description
We have seen an instance where a very large oplog resulted in increasing memory usage (leak) – the suspicion is that the truncate call is somehow leaking memory. We should write a test that exercises very large truncate ranges and see if we can reproduce the behavior.
Attachments
Issue Links
- duplicates
-
SERVER-44740 huge oplog configuration causes memory use to grow without bound
-
- Closed
-