Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
455 results found
-
Find Database on Multiple Cluster
Enable the search box on Database Deployments to search for a particular database on all clusters under the project.
This would be helpful when having different databases on many isolated clusters.
1 vote -
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.
4 votes -
Allow multiple VPC CIDR ranges in Peering connection
Allow multiple VPC CIDR for a single Peering connection from Atlas to AWS.
Our AWS account has two CIDR ranges for a single VPC. Atlas peering connection only allows connection to a single CIDR range.
Today, I need to create a separate private link connection to be able to connect to the second CIDR range.22 votes -
Feature: Atlas UI -- Star/Favorite/Bookmark of Project
It would be nice to be able to star/bookmark projects, so I don't have to type half the project name in every time I switch between environments--eg. like in Datadog, star a dash board and it shows up at the top of the list/without search
2 votes -
Memory managed on the mongodb atlas nodes
we recently had a major outage due to OOM on the mongodb shard nodes . we would suggest help preventing this by providing below features so this can be managed properly going forward
- Set the memory allocated to the WireTiger Cache
- Configure more memory for a tier. The current tier is M50 (8 vCPUs, 32GB memory). We would like to be able to allocate more memory for M50 to handle more connections and memory use for workloads. Scaling up to M60 will double the vCPUs to 16 which we do not want. Perhaps offer tier with high memory usage for…
1 vote -
Support exporting Custom routes
Supporting export of custom routes with peering connection (with GCP in our case). At this point it's not possible to access atlas from our on-prem network with -priv FQDN, we would have to use the public ones by managing source ip in GCP firewall (painful on a remote workers world) or adding a Google Cloud VPN product to create some kind of vpn connection. Just permitting export of private subnets would be great !
We have peering with other product and they support it !2 votes -
og the size of oplog-mongomirror.bson.sz at time of deletion in mongomirror logs
currently when we run the mongomirror with --oplog, it does the status when it is deleted.
It will be good , to add the size information ofoplog-mongomirror.bson.sz, that will help us to decide the appropriate disk .1 vote -
Allow private dns names for Atlas private endpoints
When a customer requires the use of private DNS names for their Atlas private link connection strings, can we allow them to switch on this capability? Basically use a private dns zone instead of a public one and share it as part of the VPC endpoint setup? AWS seems to offer this capability. See this link here https://aws.amazon.com/about-aws/whats-new/2020/01/aws-privatelink-supports-private-dns-names-internal-3rd-party-services/
8 votes -
Approval workflow for database deletion
The current Termination Protection only prevents accidental deletion of a cluster. It helps to have a similar protection to databases inside the cluster.
Even better if there is an approval workflow, in which several people must accept before a database/cluster is deleted.
2 votes -
secrets versioning for database users
We would like to have secrets versioning on atlas end so that secrets rotation is easier - as it is a periodic procedure in most companies, would be great to refer to a new secret version of an existing user instead of recreating the user.
also considering this is sadly not gonna be handled https://feedback.mongodb.com/forums/924145-atlas/suggestions/44283477-vault-should-return-users-only-once-they-can-be-us would be cool to make rotation easier.1 vote -
There is a grammatic error in button text.
The button says "Do not me show again"; it should say "Do not show me again".
Thank you,
Alpesh1 vote -
Change shortcut for GOTO
The current shortcut (CTRL + SPACE + TAB) for the GOTO functionality is incredibly annoying as it results in a tab switch in Chrome, and it's also quite slow to reach for a shortcut.
A suggestion would be to use CTRL + K which usually in Chrome is "Search on Google", but it's also used by GitHub for their version of "GOTO", so pressumably a whole lot of people are already used to it.
1 vote -
mongoexport - generate multiple compress files as output
This is a feature request for https://github.com/mongodb/mongo-tools/blob/master/mongoexport/main/mongoexport.go
- similar to s3.format.maxFileSize parameter in ADL $out, cut a new file every xxxMB
- similar to s3.format.columnCompression parameter in ADL $out, use gzip/zstd to compress the output BSON or JSON
- support write to locally-mounted file system (EBS/NFS) and cloud object store S3/GCS
The similar logic has probably implemented in the ADL $out codebase already, we just need to port them over to mongoexport
1 vote -
Add hint support for MongoDB API functions
The "hint" option for Mongo Shell query/write operations is very useful when the Query Planner does not select the right index by default, or just to make sure the right index is used. When you cannot use the "Hide index" feature on the index selected by default, "hint" becomes the only way to have an efficient IXSCAN.
However, the "hint" feature does not exist on the MongoDB API functions (https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/). This means that no command we can run inside a Trigger can specify a "hint" option.
I think that "hint" is a great "backup" feature for cases where…
2 votes -
Implement SCRAM-SHA-256 mechanism for Atlas or make a SCRAM-SHA-1 as default
The main problem is inconsistency in the default authentication mechanism of clients and Atlas.
This causes a failover from SCRAM-SHA-256 to SCRAM-SHA-1 by clients on authentication failure.
This causes a huge number of errors in "Database Access History" which becomes useless.
1 vote -
MongoDB Connection Pool Proxy
Currently there is no Connection Pool proxy supported by MongoDB.
With the ever increasing use of serverless and containers, clusters will need to be over provisioned in order to account for the increased connection counts.
A better solution would be a Connection Pool proxy allowing for a many-to-one relation for connections to MongoDB.
In the case of Lambda, this would reduce the number of Zombie connections (Connections that have been terminated on the Lambda side but are still open on the server side.)
3 votes -
Option to deploy the databases with pinned version.
Atlas by default picks the latest patch when we create the databases for any major version. It would be helpful if the customers can choose and control the minor version of the databases(including patch version) when we deploy the cluster. For example: We want to deploy the databases with 4.2.19 but the Atlas is automatically creating 4.2.22
This will help us identify any application dependencies on any particular patch version during our migration to Atlas, also this will help us test the patch versions in dev/lower environments before we promote the version to production.
This feature is important for us…
3 votes -
Mongo Atlas - Pause Cluster protection
Mongo added a feature where termination protection option has been added.
pause cluster protection is needed as well to prevent mistakes7 votes -
Atlas shards with different clusters tiers
For solutions of hot and cold storage, there is at least 2 options:
- Online archiving
- Hot and cold cluster (using a trigger and datalake)
But these solutions have limitations (https://www.mongodb.com/docs/datalake/limitations/)There is another solution: using sharding.
We can set shards like so:
1 shard: Data from the last 2 months -> Hot data
1 shard: Data between 2 and 24 months -> Warm data
1 shard: Data more than 24 months -> Cold dataThe usage pattern: 95% of the accesses/queries go to shard with the hot data.
On Atlas, we need to set the same…2 votes -
Test maintenance effects
While Atlas provides the 'test failover' feature, this only takes effect on the primary of each shard. Customers who run large sharded clusters on Atlas require testing the effects of a full maintenance patch that would restart all mongod's and mongos's, config servers, etc. This feature is a request to improve the chaos engineering features of Atlas.
At present, customers are being advised to change the TLS version of the cluster which could force restarts of all mongod's, mongos's and config servers. While this may be acceptable in non-production environments, it is unlikely in production environments.
I believe there's an…
3 votes
- Don't see your idea?