Skip to content

Atlas

← MongoDB Feedback Engine
Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

How can we improve the platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

25 results found

  1. 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
    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

  2. 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
    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

  3. 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
    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

  4. 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
    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

  5. 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
    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?
2 Next →
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)