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

huge oplog configuration causes memory use to grow without bound

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • ALL
    • Execution Team 2019-12-16

      In a customer case configuring the oplog to 3TB resulted in memory usage growing over time, apparently without bound.

      Reducing the oplog size resolved the customer issue, but doing some testing around huge oplog configurations seems warranted.

      EDIT:
      Apparently the size of the oplog was not reduced, however, metrics show the application reduced the amount of oplog GB/Hr. Obviously this introduces the possibility that oplog deletion is lagging, it's not the size of the oplog that is the principle concern. 

        1. diag.zip
          127.69 MB

            Assignee:
            rachelle.palmer@mongodb.com Rachelle Palmer
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: