[SERVER-44646] Test oplog stone behavior with very very large oplogs Created: 14/Nov/19  Updated: 06/Dec/22  Resolved: 20/Nov/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-44740 huge oplog configuration causes memor... Closed
Related
Assigned Teams:
Storage Execution
Participants:

 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.



 Comments   
Comment by Eric Milkie [ 20/Nov/19 ]

Closing in favor of SERVER-44740

Generated at Thu Feb 08 05:06:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.