Skip to content

Atlas

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

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

24 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Storage autoscaling of storage should also occur when Atlas searches are being rebuild

    When the storage requirement exceeds the available storage when rebuilding Atlas searches a warning is issued and manual intervention is needed.

    I would like that autoscaling of storage will occur when needed for rebuilding Atlas indexes.
    This would save us time and no need to react to warnings.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Autoscaling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base