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

huge oplog configuration causes memory use to grow without bound

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Execution Team 2019-12-16
    • Case:

      Description

      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. 

        Attachments

        1. diag.zip
          127.69 MB

          Issue Links

            Activity

              People

              Assignee:
              rachelle.palmer Rachelle Palmer
              Reporter:
              keith.bostic Keith Bostic
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: