[SERVER-45855] The 'Top' command managing its own data in the UsageMap is error prone which causes memory leaks Created: 30/Jan/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45137 Increasing memory allocation in Top::... Closed
Assigned Teams:
Query Execution
Participants:

 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.


Generated at Thu Feb 08 05:09:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.