Memory managed on the mongodb atlas nodes
we recently had a major outage due to OOM on the mongodb shard nodes . we would suggest help preventing this by providing below features so this can be managed properly going forward
- Set the memory allocated to the WireTiger Cache
- Configure more memory for a tier. The current tier is M50 (8 vCPUs, 32GB memory). We would like to be able to allocate more memory for M50 to handle more connections and memory use for workloads. Scaling up to M60 will double the vCPUs to 16 which we do not want. Perhaps offer tier with high memory usage for same number of vCPUs. We discussed this with the support engineer so you can get more details from him. 3.Ability to cap the number of connections on the to prevent a connection storm
1
vote
![](https://secure.gravatar.com/avatar/f14ebcb2d5bfcd91230b981216dd8f28?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)