Release system's memory after index creation


We have a MongoDB atlas cluster (replica set - 3 nodes - M50) and one of the replicas uses more than 85% of the system’s memory after an index creation and won’t go down.

I saw that MongoDB doesn’t free up memory by default and we could set tcmallocAggressiveMemoryDecommit to enable this behavior, but when I try to do it, I receive a not authorized error.

I can’t contact support because I don’t have a Developer or Premium support.

Can someone help me?


Hi @Felipe_Gaudio - Welcome to the community.

You can contact the in-app chat support which doesn’t require a developer or premium support subscription. In saying so, you may wish to confirm the topic of this memory release is within support scope for the Atlas support team.

However, could I ask how much of a spike in memory you saw during this time in GB? Additionally, what is the metric you monitored for this? (System Memory, Memory, etc)

Lastly, do you have any details that you could provide regarding the index created? E.g., The create index command issue, whether it was an Atlas search index, etc.

Look forward to hearing from you.