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

The 'Top' command managing its own data in the UsageMap is error prone which causes memory leaks

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Querying
    • Labels:

      Description

      After diagnosing a customer issue (SERVER-45137) where Top was allocating memory to record collection information and not deallocating it once the collection was removed, I believe we should set out to improve the 'Top' command in regards to its data management.

      Forgetting to clear collection information from Top comes with consequences, such as running out of memory for long enough running processes. We should have a mechanism in Top that guarantees the collection information will be cleared once the collection is dropped. Making the Top data as a decoration on the collection is one way we could ensure this, it would even handle a collection rename for us.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-query-execution Backlog - Query Execution
              Reporter:
              gregory.wlodarek Gregory Wlodarek
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated: