Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
479 results found
-
Atlas dedicated tier is not actually dedicated
MongoDB Atlas, despite the documentation and Atlas UI reflecting M10+ as dedicated tier, is not actually dedicating all resources. While CPU and Memory can be considered dedicated, storage is not dedicated until M300+. After working with MongoDB Support, and support working with AWS support, our performance issues were identified by a noisy neighbor who was choking our disk IOPS even though we are running M40_NVME clusters which are supposed to be high performance.
MongoDB should at a minimum highlight this as a consideration for latency sensitive deployments.
A new Atlas alert should be created to identify issues where slow query…
5 votes -
Altas CIDR ranges for network containers are too restrictive
Background:
For each MongoDB Altas project, the clusters built in that project are built using a "network container", which tells MongoDB Atlas which pool of IPs it can select from given a CIDR range for its underlying infrastructure.AWS minimum imposed CIDR value/subnet size: /28
MongoDB minimum imposed CIDR value for clusters deployed to AWS: /24Azure minimum imposed CIDR value/subnet size: /29
MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21For customers who elect connecting to MongoDB Atlas via VPC peering, they know that IP space is a scarce resource. Reserving /24 or /21 IP space…
5 votes -
Atlas project capacity should be discoverable
Atlas project capacity should be discoverable. Based on documentation, it seems project capacity is dependent on various factors and can be arbitrarily increased via support request. We currently do not know how many clusters/nodes we have available to deploy in a given project and that is critical information to inform planning at scale.
5 votes -
Integrated Benchmark utility for mongodb
I would like to request a mongodb utility which can do benchmark tests and can be used by developers and DBA to test mongodb for release changes, application code changes etc. The utlity should be able to simulate multiple users and produce different types of workloads (like reads, updates, deletes, inserts etc). This would need to be similar to other nosql benchmark tool like asbench used in aerospike nosql database.
Link is : https://docs.aerospike.com/tools/asbench5 votes -
Add more information to "We are deploying your changes..." blue bar
Occasionally we see the deployment blue bar but aren't sure exactly what is being done. It would be very useful to have a link to click to see what changes are currently being pushed out.
5 votes -
AWS multi-region key (CMK)
While using AWS multi-region key, if a customer selects a new region for their CMK, Atlas will trigger a key rotation process which could take some time to complete depending on the disk usage. Can we introduce native support for AWS multi-region key so Atlas does not have to re-encrypt data if CMK ID is the same in the new region.
https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html
5 votes -
Transactions support for Merge operation in aggregation pipeline
Hi Team,
can we consider supporting the transactions when we use $merge stage in mongodb aggregation pipeline?
https://docs.mongodb.com/manual/reference/operator/aggregation/merge/#restrictionsWe have a requirement where we need to use the merge stage in pipeline and we would like to ensure automaticity in the transaction.
The aggregation pipeline we are building can merge multiple documents into the same collection and we would like to have either all or none by using transactions and the current merge operation cant support it.
thank you
5 votes -
Atlas Shard Management
Currently the Atlas UI only presents options for how many shards a cluster can have.
Putting in a suggestion to perhaps allow similar functionality / features to Cloud Manager's shard management as shown : https://docs.cloudmanager.mongodb.com/tutorial/manage-data-sharding/#manage-sharded-collections
5 votes -
Add Cluster name to process list api
Currently the processes API (https://docs.atlas.mongodb.com/reference/api/processes-get-all/) returns only the ReplicaSet name of the process not the cluster name, while the cluster API (https://docs.atlas.mongodb.com/reference/api/clusters-get-all/) returns the replicaset name only in the MongoDB URI.
If you have multiple clusters in the same Atlas project and you list the processes is difficult to make an association between MongoDB processes and the Cluster (Atlas UI name)
Would be nice to have also the cluster name in the processes api
5 votes -
Show index build percentage in the UI
During an index build from atlas the only status update you see is:
"We are deploying your changes (current action: configuring MongoDB)"When checking the logs of the replicaset memeber you can actually see the percentage of completion on that member of the replicaset:
2020-11-25T11:15:44.002+0000 I - [conn12] Index Build: 54798100/206784433 26%
It would be nice to have this percentage displayed through the UI.
5 votes -
Allow customers to download Atlas BI Connector process logs (similar to MongoDB Server logs)
What is the problem that needs to be solved? Customers are willing to troubleshoot / analyze Atlas BI Connector logs by themselves (they would like to investigate schema sampling timings, SQL/MongoDB query optimizations, connectivity issues, etc.).
Why is it a problem? (the pain) Currently available Download Logs option on Atlas Clusters does not include Atlas BI Connector process logs.
5 votes -
Live Migrate through VPC peering connections
Many teams put their databases in subnets without internet access or with just a NAT gateway. It would be great if the Live Migrate could be use through already configured VPC peering connections.
5 votes -
Include cluster node list in getOneCluster
Include cluster node information for all nodes in the cluster in the response JSON for the getOneCluster API call. As hostnames are needed for other API calls, there ought to be a better way to get cluster node names.
5 votes -
Allow multiple Billing emails
Allow multiple billing e-mails instead of just one. There are multiple people in our org who want a copy of the invoices, but I don't want them sent to the entire org (which is what happens if there's no billing e-mail)
5 votes -
Mongodb Atlas Malaysia AWS regions
Malaysia region is poised to be the largest AWS region and it is pertinent that Atlas can support it for south east asia. Writing in to petition of this region's support.
4 votes -
Unblock users in Russia and Belarus
Currently MongoDB blocks access to MongoDB Atlas for users who are located on the territory of Russian Federation, Belarus (and other countries).
MongoDB Support team confirmed this is the case and stated that the reason is US regulations and sanctions, referring only to the blog post published on their website (https://www.mongodb.com/blog/post/mongodb-assistance-ukraine-shut-down-work-russia). The blog post does not mention that the access to users is blocked.
To our best understanding not many other tech companies have implemented such strict measures.
We've also taken the time to delve into the sanctions topic and have reviewed every public release of sanctions on…
4 votes -
AWS gp3 Decouple IOPs from Disk Size
With AWS EBS gp3 volumes, IOPs and throughput can be provisioned separately from EBS storage size. While Atlas now uses gp3 volumes and provides a base throughput of 3,000 IOPs, higher throughputs are still directly tied to disk size.
We run IO-intensive workloads that require high throughput, and we have to severely over-size disks to get the needed throughput. We don't require the extra-low latency of provisioned IOPs (which is much more expensive than over-provisioning storage).
According to the linked AWS documentation below, if the M60 instance size is running on an ec2 m5.4xlarge instance type, it can support a…
4 votes -
Support for GCP Saudi Arabia/Dammam me-central2 for Atlas
GCP announced availability of services in me-central2. Can MongoDB please support this region in GCP?
4 votes -
LDAP Users shouldn't be successfully authenticated if not authorized
Today, if you login with proper LDAP credentials to an Atlas cluster, you are authenticated into that cluster, even if you are not authorized to have access. This is not at all how databases should work, nor is it how most databases do work today. If a user is not authorized, that connection should fail immediately.
Allowing successful authentication, even when not authorized, can increase the security vector for ddos attempts as well as causes confusion when successful attempts are logged, even though the user was not authorized to see data.
Please reject any non-authorized user from connecting to an…
4 votes -
Google Private Service Connect
Greeting from Fivetran!
This is somewhat related to https://feedback.mongodb.com/forums/924145-atlas/suggestions/45272014-allow-customers-to-specify-the-number-of-service-a . Having 50 service attachments is not scalable for us which requires 50 IP addresses for each PSC. We have a large customer base and having each of them create PSC would require a lot of IP addresses and would quickly exhaust our subnets.
From the support case it seems that the decision to use 50 PSC attachments comes from the fact that GCP load balancer does not allow more than one pool of servers per service attachment and that the ports are passed through as is as opposed to AWS…
4 votes
- Don't see your idea?