Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

Database

Showing 302

Make it possible to delete a database via API

It would be nice to be able to delete a database in a replica set via an API call. This would make it easier for CI/CD when deleting clients Strange thing is that I can delete a complete cluster, but more fine-grained deletion is not possible. lik...
Guest almost 4 years ago in Database 1 Submitted

Should be possible to configure profiling output destination

When enabling database profiling the output is sent to both the system.profile collection and system logs. Logging to a capped collection is fine but spamming the logs on disk is not good. We have a need to be able to react to changing query patt...
Guest over 2 years ago in Performance & Optimization 0 Submitted

Validation should support default values

Various users feel that validation should support default values. See, for instance: https://www.mongodb.com/community/forums/t/support-default-value-in-schema-validation/319684 https://www.mongodb.com/community/forums/t/setting-default-values-in-...
Guest 10 months ago in Data Modeling & Indexing 0 Submitted

Higher IOPS for small disk sizes (MongoDB Atlas on Azure)

AWS and GCP start with 2300-3000 IOPS for M10+ instance from the smallest disk size (8Gb), whereas on Azure we get 120 IOPS with 8Gb, 240 with 64Gb, 500 IOPS with 128Gb ... nowhere near to what AWS/GCP offer (120 - 500 IOPS for a database server i...
Guest over 4 years ago in Database 2 Submitted

Release notes with urgency and risk

Provide MongoDB customers/users with an understandable release notes, especially for bugfixes. **What are the risks this bugfix release covers, what is its urgency**. Right now, release notes are made of MongoDB Jira tickets, which are very detai...
Guest almost 4 years ago in Database 0 Submitted

Lock on session start level with provided keys

Scenario: Parallel DB updates with transactions on multiple collections that use same documents. Example: Calculate some common stuff to embed it in extra collections to avoid lookups. Problem: Lock and timeout on documents uses up valuable time ...
Guest over 2 years ago in Storage & Transactions 0 Submitted

Allow the ability when NVME cluster to autoscale up based on CPU and Memory

To provide autoscaling capability for MongoDB NVME clusters based on CPU utilization and memory metrics. This feature would automatically provision additional resources when predefined thresholds are reached, ensuring optimal performance during us...
Guest about 1 year ago in Performance & Optimization 0 Submitted

Allow kill connections

Kill session commands only stop current activities on DB, but not closing/dropping connections (connections still remain open in $listSessions). It´d be useful to be able to close opened connections in situations where too many sessions have been ...
Guest almost 6 years ago in Database 0 Submitted

Disallow new connections that don't specify an appName field

Currently as a DBA it's sometimes hard to identify which service is causing load on a shared cluster/database. Some people connect for adhoc workloads but don't specify an appName making it hard to track back to the owner. It would be useful to re...
Guest about 1 year ago in Database 0 Submitted

Raise the limit of 16 MB JSON between aggregation stages

When doing analytics, the 16 MB JSON limit between aggregation stages restricts the ability to process large amount of data. allowDiskUse does not help with all the various $operators and stages that we use. See ticket 00774514 for details.
Guest almost 4 years ago in Querying & Aggregations 0 Submitted