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

Possible memory leak in 4.0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 4.0.11
    • Fix Version/s: None
    • Component/s: Networking
    • Labels:
      None
    • Environment:
    • Operating System:
      ALL
    • Sprint:
      Repl 2019-10-21, Service Arch 2019-11-18, Service Arch 2019-12-02, Service Arch 2019-12-16

      Description

      Good day.

      After upgrading to 4.0 we've encountered some sort of memory leak in 2 cases:

      1) In cluster environment described in SERVER-43038. I don't have diagnostic.data from that time, but possibly can extract some logs from our logging system.
      Memory leak occured after we've shutdown our slaveDelay instances and lasted until we've started them again.

      2) Recently in replica set configuration (i attached mongodb memory graphs from two servers (each one was primary at some time), server logs, diagnostic.data and configuration file).

      Spike around 2-3pm 19.09 on db1-1 was restoration of 'drive' database with mongorestore. Also i did a rs.stepdown() and restart server intance db1-1 at 4:30pm 21.09 due to memory pressure (memory leak has moved to the new primary). At 11:25pm 21.09 we've disabled most of the processes that work with that replica set.

      After i've started workload again i cannot reproduce memory leak. On the contrary you can see resident memory decreases on db1-2 from 3pm 23.09 and up to date)

        Attachments

        1. diagnostic.data-drive1-db1-1.tar
          124.90 MB
        2. diagnostic.data-drive1-db1-2.tar
          111.54 MB
        3. dorado1-memory-update1.png
          dorado1-memory-update1.png
          32 kB
        4. drive1-db1-1-memory.png
          drive1-db1-1-memory.png
          38 kB
        5. drive1-db1-1-part1.log
          148.87 MB
        6. drive1-db1-1-part2.log
          74.49 MB
        7. drive1-db1-2.log
          41.90 MB
        8. drive1-db1-2-memory.png
          drive1-db1-2-memory.png
          41 kB
        9. drive1-db1-memory-update1.png
          drive1-db1-memory-update1.png
          33 kB
        10. driveFS-18-memory-update1.png
          driveFS-18-memory-update1.png
          34 kB
        11. driveFS-2-memory.png
          driveFS-2-memory.png
          52 kB
        12. mongodb-drive1-db1.conf
          0.4 kB
        13. Screen Shot 2019-09-30 at 12.15.18 PM.png
          Screen Shot 2019-09-30 at 12.15.18 PM.png
          160 kB

          Issue Links

            Activity

              People

              Assignee:
              ben.caimano Benjamin Caimano
              Reporter:
              vergil Alexander Ivanes
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: