Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
26 results found
-
Auto downscale - Scaling down during peak moments
The auto downscale checks for the average of usage for the last 4h. But, sometimes we have a cluster with little usage for almost all the 4 hours, but at the last 30, 15 minutes, it starts to consume more CPU (something higher than 60% or even higher).
As the autoscale only checks at the last 4h it sometimes happen that a cluster does a auto downscale when it shouldn't. A litler time after it needs to scale back up because the usage goes higher than 90% (or at least higher than 75%)
It would be much better if the…
2 votes -
GCP eu-southwest-1 Madrid Atlas region
Would love to deploy the cluster in the recent GCP eu-southwest-1 region. It is already running, and would be a plus for all Spanish customers reducing latency. It does not yet appear in the Atlas cluster creation page.
2 votes -
we should be able to develop library of ML algorithms as plug-ins
we should be able to plug in the already developed algorithms say from GitHub or any other repository
2 votes -
Enable Replica Set Scaling Mode
Currently, it's not possible to configure the replica set scaling mode for shards and other configs available in the UI through terraform (see attached screenshot).
1 vote -
limit the size of tmp files created as part of $sort stage
Our docs says, "Starting in MongoDB 6.0, pipeline stages that require more than 100 megabytes of memory to execute write temporary files to disk by default."
These 'temporary files' can take up ALL the disk space if auto storage scale isn't turned on and crash the cluster.
1 vote -
Modify MongoDB Autoscaling Logic for CPU Usage Interval
Currently, the autoscaling feature in MongoDB is configured to initiate scaling based on the last 1-hour CPU usage. The trigger for autoscaling is set at 75% CPU usage within this hourly interval. However, there is a requirement to adjust this logic to a more granular level.
Request:
The request is to modify the autoscaling logic in MongoDB to consider the last 30 minutes of CPU usage instead of the current 1-hour interval. Specifically, scaling should be triggered if the CPU usage exceeds 75% within the last 30 minutes.
1 vote
- Don't see your idea?