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

MongoD memory usage higher than wiredTigerCacheSizeGB for primary in replica set

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      3 node replica set on Windows (2 replicas and one arb).

      Show
      3 node replica set on Windows (2 replicas and one arb).

      Description

      I've been watching mongod memory fairly closely (SERVER-20991,
      SERVER-20104 etc). With 3.2, memory usage on my non-replica-set deployment is excellent and it is well within expectations for the given wiredTigerCacheSizeGB.

      Testing a replica-set with the same workload, the memory appears to push past this limit significantly: using a 4GB argument, actual memory usage is at 6.5 GB fairly quickly after kicking off the run.

      I haven't done a full run yet, but will attempt to do so to see if memory keeps climbing or if it levels off.

        Attachments

        1. memory.png
          memory.png
          174 kB
        2. memory-early.png
          memory-early.png
          167 kB
        3. metrics.2015-12-16T05-49-34Z-00000
          9.45 MB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              nick@innsenroute.com Nick Judson
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: