Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
457 results found
-
Make BI Connector Settings Permanent
Allow the "SET GLOBAL mongodbmaxvarcharlength = n" to be permanent after a Mongosqld restart. Currently, the setting is ephmeral and must be set everytime the mongosqld daemon is restarted. Currently, our production environment mongosqld can restart without our knowledge at anytime. This results in the mongodbmaxvarharlength variable being reset to zero, which can lead to a production outage. Is there anyway this can be automated, maybe through database trigger?
33 votes -
Enable and disable balancing on a collection
Shell commands sh.enableBalancing() and sh.disableBalancing() were not permitted on Atlas hosted MongoDB. Is it possible to grant this permission?
Currently it failed with error:
…
uncaught exception: Error: command failed: {
"ok" : 0,
"errmsg" : "not authorized on config to execute command { update: \"collections\", ordered: true, writeConcern: { w: \"majority\", wtimeout: 60000.0 }, lsid: { id: UUID(\"ed83ed26-e07b-4f34-a90a-a145bbe58a48\") }, $clusterTime: { clusterTime: Timestamp(1646788928, 17), signature: { hash: BinData(0, 347249E35ED43BDADAE12FB0F794C091CB86206E), keyId: 7052082196881866761 } }, $db: \"config\" }",
"code" : 13,
"codeName" : "Unauthorized",
"operationTime" : Timestamp(1646788928, 18),
"$clusterTime" : {
"clusterTime" : Timestamp(1646788928, 18),
"signature" : {
"hash" : BinData(0,"NHJJ417UO9ra4S+w95TAkcuGIG4="),
"keyId"1 vote -
Migrate to new cluster without auto upgrade (5.1.0)
Hi,
Our clusters are in auto upgraded feature of MongoDB versions right now.We want to stop the auto upgrade feature for now and migrate our clusters to new one with the MongoDB version 5.1.0.
But, when we try to create a new cluster it's not showing the option for version 5.1.0.
And we need 5.1.0, because we're going to restore the data from the current cluster which is versioned 5.1.0.Your help is much appreciated.
2 votes -
connecting from ubuntu to mongodb atlas is terrible
kamal@zehan:~/Desktop/mongodb$ mongo "mongodb+srv://cluster0.d9ct7.mongodb.net/myFirstDatabase" --username mongo
MongoDB shell version v5.0.5
Enter password:
connecting to: mongodb://cluster0-shard-00-00.d9ct7.mongodb.net:27017,cluster0-shard-00-02.d9ct7.mongodb.net:27017,cluster0-shard-00-01.d9ct7.mongodb.net:27017/myFirstDatabase?compressors=disabled&gssapiServiceName=mongodb&ssl=true*** You have failed to connect to a MongoDB Atlas cluster. Please ensure that your IP allowlist allows connections from your network.
Error: bad auth : Authentication failed. :
connect@src/mongo/shell/mongo.js:372:17
@(connect):2:6
exception: connect failed
exiting with code 11 vote -
Force restart of unhealthy node
Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.
If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)
103 votes -
Atlas policies
In the MongoDB atlas portal, there should be a way to configure policies across an organization. ie: policies to restrict users from creating clusters from certain cloud providers (ie: azure), restrict users from creating databases of a certain size, etc.
7 votes -
Restrict specific users or client IPs to only Analytics node(s)
There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.
Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…
20 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 -
Purge of unused accounts after X days/months
After X number of days/months (say 12 months), accounts that haven't been accessed or have never been accessed go into a 3 month freeze period, before they are automatically disabled and deleted. A report of such accounts should be auto generated and archived. The freeze period intention sends a warning to the account holder as well as an alert to administrators of the atlas org.
2 votes -
Compact collection from UI
Compacting of a collection directly from the MongoDB Atlas website UI.
No need to run CLI commands and changing primary database.
Making regular maintenance easier.
26 votes -
Atlas should allow deployments of non-voting members on region for tiebreaking purposes
No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.
This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.
1 vote -
Feature Request: DNS record per zone for global cluster
Today Atlas creates a single DNS record for the global cluster which has SRV records pointing to all servers in the cluster across all zones.
This causes issues when a service hosted in US tries to use this DNS record as it now connects to every server in the SRV list of the DNS record. We ideally would want the US service to connect to its closest mongos router (US zone) and not all the mongos routers as it is unnecessary waste of resources. Our workaround today is to manually pick the servers and build the connection string in old…
1 vote -
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
4 votes -
Specific Privilege selection on Org Level
It would be great to select specific privileges for on the Organization Level as well. Similar to what one can do on the Project Level. E.g. Org Member but without being able to see billing.
1 vote -
Allow the ability for a rolling cluster restart like during maintenance
Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.
17 votes -
Create distinct indexes for Analytics nodes
To effectively use Workload Isolation, it is desirable to have different indexes on the operational cluster nodes than the indexes used to support analytics and reporting query patterns. It would be powerful for Atlas to enable different indexes on Analytics nodes.
36 votes -
B2B marketing is pretty slow
We had just migrated to another platform probably we did not approach you earlier
Target all Users of SAP !
1 vote -
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 -
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 -
Improve handling of ROLLBACK state
Recently we had a member of a replica set in a sharded cluster enter
ROLLBACK
state. We just happened to notice it in an automated email sent by Atlas about primary elections which showed one of the members inROLLBACK
state.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
- Don't see your idea?