Test oplog stone behavior with very very large oplogs

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: