Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-44646

Test oplog stone behavior with very very large oplogs

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Storage
    • Labels:
      None

      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

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: