Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
468 results found
-
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 -
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 -
disabling mongo user
Instead of completely removing a Mongo database user, its better if there is option to disable user so that if there is any untoward incident we can enable it back. After observing for some time, we can delete/disable the user based on organization requirements. Its useful in some cases like mongo db user returned to same department after some time .
3 votes -
Support NVMe for Atlas Azure
Support NVMe disk for MongoDB Atlas Azure.
3 votes -
Copy/Duplicate Cluster configuration
It would be really useful to create a new cluster based on an existing configuration.
Snapshots are supposed to be loaded into clusters of the same configuration, but having to set up the configuration manually is prone to human error. Having an option to copy the cluster configuration would be helpful.
Support suggested the following workarounds, but the option should really exist in the UX, given that snapshots can be taken and loaded in the UX.
- use the API to create all clusters so that the config exists in code
- use terraform to create clusters3 votes -
Feedback and public roadmap.
I have voted and written since 2020 several improvement ideas for your platform.
Being a client for a major insurance company, I'm disappointed to see that for several suggestions dating back more than 12 months, it doesn't even seem to have been looked at by your team.
It would be more than interesting to have an idea for your roadmap as well as a dynamic management of the catalog of ideas (feedback) maintained by your customers.
I consider this a lack of respect for your users and customers.
Some examples:
https://feedback.mongodb.com/forums/924145-atlas/suggestions/40638277-atlas-backup-to-second-region
https://feedback.mongodb.com/forums/924145-atlas/suggestions/43289796-max-database-users-not-visible
https://feedback.mongodb.com/forums/924145-atlas/suggestions/42163234-authentication-on-azure-iam
3 votes -
Warm up cache automatically when there is any server/node restart events
Usually it takes hour or so for the cache to warm up depending on the data size when an server restart scenario occurs ( increasing the tier / storage etc). And there are alternatives like running cache warm up queries to bring the nodes up to speed .
However if this cache warm up should be inherent and automatic for the server restart scenarios .
3 votes -
Add the In-Memory Storage Engine to Atlas
Enable the use of the in-memory storage engine in atlas shards. That way atlas users can get the same level of functionality as enterprise. Atlas is a great platform, but not being able to use an in-memory storage engine replica set in a shard is a huge letdown (at least for me).
3 votes -
Support Linode as a cloud service
Linode is a widely used cloud provider between developers that do not like the outrageous interface & costs of the main providers (Google, Atlas, AWS). Linode has free in-network bandwidth as well, making for private connections to be much cheaper.
3 votes -
Add a simple log filter in the Atlas log API call
In the Atlas log API call, add a new Request Query Parameter which allow people to set a phase or string, to avoid downloading log lines including this phase or string.
So people don't have to download large quantity of log messages that they don't need.
For example the the NETWORK log message between replica-set members.
3 votes -
Improve handling of ROLLBACK state
Recently we had a member of a replica set in a sharded cluster enter
ROLLBACKstate. We just happened to notice it in an automated email sent by Atlas about primary elections which showed one of the members inROLLBACKstate.Fortunately for us the writes which had been reverted were not critical and we were fine with that. However, this could have resulted in serious data loss which could have gone unnoticed until a customer reached out to us.
The handling of a situation like this one should have been much better and more user friendly. We should have…
3 votes -
Access key expiration date
We would like to have option set expiration date time while creating API access keys and also ability to check expiration options through API.
3 votes -
Preserve Oplog upon storage downgrade in Azure
Oplog was wiped out upon storage downgrade from 128Gb -> 16Gb, even though the database size incl. oplog was less than 2-3Gb.
Please change the downgrade procedure to NOT wipe out the oplog.
This was tested/experienced on Azure.
3 votes -
Document Atlas Cluster Tier Performance Expectations
Document approximate Atlas cluster tier performance expectations that application development teams could reference when requesting an Atlas cluster (IOPS, max connections, network performance).
This information is currently available in the Atlas UI.
Other cloud providers such as CloudAMQP do this: https://www.cloudamqp.com/plans.html.
3 votes -
Create TTL index based on local timezone as opposed to UTC time
Create TTL index based on local timezone as opposed to UTC time
3 votes -
Allow domain or URL for whitelisting
Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.
3 votes -
Improve Cluster Name Limits
Cluster names currently impose the following limits:
Cluster names shorter than 23 characters can't end with hyphen or dash (-)
Cluster names 23 characters or longer can't use a hyphen or dash (-) as its 23rd character.
Instead, we should either trim or replace the hyphen at the end of a 23 character name.
3 votes -
migration should check actual disk space used by source MongoDB
The easy migration system seems to check the total disk space used on the source machine, and does not discriminate between that disk space used for MongoDB (which will be needed on Atlas) and those used for other applications.
Because the source system contains a lot of logs and a complete copy of our databases in different folders, we have had to configure Atlas to use >2x the actual disk space it'll need.
3 votes -
support external nodes
Allow manual addition of externally-hosted non-voting (hidden) node(s) to an Atlas cluster. This would permit:
- compliance with data management rules that require a copy of all data to be kept in-house (ie outside cloud)
- easier migration out of Atlas for real-time DB use cases where a stop/backup/restore is not a feasible route3 votes -
geospatial
Could we please consider boosting MongoDB's geospatial capabilities by incorporating Turf.js into Atlas. I would hope this would be an integration similar to Lucene in that it exposes some functionality through the UI, and some through aggregation. It would allow us to gain a huge amount of functionality. https://turfjs.org/
3 votes
- Don't see your idea?