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

Configurable Heap Profiler Maximums

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics
    • Labels:
      None
    • Storage Execution

      Currently the heap profiler will stop collecting information once it hits a hardcoded maximum. Messages like the following will be printed out once in the logs:

      too many stacks; disabling heap profiling
      too many live objects; disabling heap profiling
      

      For situations where more data collection is necessary, it would be useful to set a different maximum so these limits don't get hit.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: