Database
307 results found
-
Update to two binding accounts in the config file for LDAP.
Please refer the Case: 00803199
We need to update to two binding accounts in the config file to for LDAP authentication so that we can avoid down time while resetting the binding account password.
3 votes -
$populate stage
Please provide a $populate stage that allows to resolve single referenced documents.
Internally it could use the combination of $lookup and $unwind:Related:
https://stackoverflow.com/questions/37793844/mongodb-how-to-resolve-dbref-on-client-side
1 vote -
Easy Paging with offset
Paging is a common functionality for REST APIs. When implementing paging queries for large datasets skip and limit is often not an option. When using query filters with non unique fields, such as creation date there can be problems such as duplicate entities on subsequent pages. It would be great to be able to additionaly pass in an offset document reference, that would be used as a start in case the filter does not lead to a unique starting point.
so for example
db.test.find({"creationDate" : {$gte:ISODate('2021-08-27T07:25:00Z')}, {"offset":<ObjectId>).sort({"creationDate":1}).limit(20)1 vote -
Reserve connections to admin users
When the max number of connections is reached, no one can login to the database until some connections are closed or a failover is triggered (killing all the connections).
The admin users should have a few reserved connections so that they can login to the database and take actions, like kill some connections.
1 vote -
Add a $median accumulator
There is the $avg operator that returns the average of a set of values. Why not a $median?
1 vote -
Deny Network Access to MongoDB Cluster
To improve network security, please create an option to Deny specific Network Adresses to MongoDB Cluster.
3 votes -
Mongo replicaset init sync issue
When we have large size mongo replica set, we may have to take out each nodes for maintenance for few hrs or days.
In that case we have to increase size of Oplog to keep several days of transactions to resync nodes after maintanance.
If the RS headroom falls below oplog window, then we have blow away data and do init sync to add node back after maintanence.
The problem with very large size Oplog, will slow down any Change Stream process. Also it will occupy un neccasary space within collections.
Can mongo offer alternative way to constantly dump oplog…
1 vote -
Shard Drain/ Removal issue
If we have more shards, and if want to remove few shards (more than 1), we use below command.
db.adminCommand( { removeShard : "Shardname" } )
Ex, if I have Shard 1, 2, 3, 4, 5. want to remove Shard 2 & 5.
I want to remove one shard at a time to minimize impact to users , then want to remove, say Shard 2, then want to remove Shard 5.
If we do this, some chunks from Shard#2 also get moved to "Shard#5", which is suppose to removed later. This causes Shard#5 chunk size increase. Then takes more time.
…
1 vote -
Support for MongoDB Server on Ubuntu 21.04.
Per the MongoDB Server Supported Platforms Matrix support for Ubuntu 21.04 is not yet available.
We would like to see the currently supported MongoDB Server versions available on the Ubuntu 21.04 LTS distribution which was released on 22 April 20212 votes -
Implement read-only fields and documents in database
I haven't tracked down this functionality yet, so excuse me if it is already implemented.
As a developer and system administrator I came to a dilemma how to prevent myself to make changes to documents.
I can limit myself as a programmer, but as a administrator I can always logon to console and make changes ''by hand''.
I was thinking of read-only field type, which once set, could not be updated nor removed from document (although backup and restore is the first problem which comes to mind). This limit should be set on a database level. Read-only field could typically…
1 vote -
The ability to perform a quick rollback or rewind of the database
This is along the lines of a flashback, to a previous point in time say from a very impacting change to data.. A large delete or data modification event. This avoids the need to take a complete outage for hours and hours restoring TBs of data and re-applying change logs. Would be great if this could be done to the granularity of a single or multiple collections too. This could use the oplogs present locally or in the oplog store.
1 vote -
`Blocking` Flag for Explain Output
It's not always obvious which aggregation stages are blocking or non-blocking when viewing
explain
output for an aggregation command. It would be helpful to include ablocking
flag for each stage of anaggregate
command in itsexplain
output.1 vote -
Provide a KRB5_KTNAME setParameter or other config setting
The Kerberos keytab file is specified in the KRB5_KTNAME environment variable.
Could a setParameter or other config file setting "krb5KtName" be provided to allow this to be set?
2 votes -
delete logs number of days old
In the options for Mongo DB Log Settings, there is only
Max Percent of Disk
Total Number of filesA new option for
Number of Days to keepWould be useful
3 votes -
Allow changing config values without restart
It would be great if configuration changes could be effected without needed to restart nodes.
For example, audit filter, enabling/disabling different security mechanisms.
This would be especially useful for Atlas and clients with large clusters where restarts will cause a performance deficit due to cold cache after node restarts.
1 vote -
MultiTenant Abstraction
Just as a time-series collection in MongoDB 5.0 abstracts the underlying implementation of the bucketing pattern, customers who implement a multi-tenant model through separate databases per tenant run into the issue of too many dhandles and would benefit from an abstraction of the implementation of a collection-with-discriminator-field - they would be able to meet their internal compliance requirement of separate databases per customer, and would have minimal changes to their code.
1 vote -
Retrywrite error fixed in Mongodb 4.4
We have test the retry write in Atlas by using mongodb java driver in Mongodb 4.4 cluster. The error is similar to SERVER-53624(https://jira.mongodb.org/browse/SERVER-53624). The supporter respond the error will fix in Mongodb 5.0. We hope this error can also fixed in Mongodb 4.4
1 vote -
Ability to replicate the data within a cluster to another cluster
Two different scenarios. One scenario is to have a DR cluster. 2 independant clusters that are one way synced. As of right now, a custom CDC solution (custom code + Kafka) is needed to achieve this.
Another is because of latency and the requirement for data to be stored in 2 different data center, 2 indepentant mongoDB clusters that are two way synced. As of right now, a custom CDC solution (custom code + Kafka) is needed to achieve this.2 votes -
Record running queries at the time of a failover
I recently observed some failovers in a replica set that may have been related to long-running queries. However, since these queries happened only sporadically, it was hard to track them down. Since the queries didn't finish, they weren't present in the logs at the time of the crash.
It would be useful if it could be possible to somehow capture the long-running queries that were running at the time that something went wrong. I recognize that this is potentially impossible, since once something has gone wrong it can be difficult to do anything.
We ended up being able to diagnose…
2 votes -
Support for Ubuntu 20.4 in MongoDB Server version 4.2
Per the Server Support Matrix https://docs.mongodb.com/manual/installation/ support for Ubuntu 20 is in MongoDB Server version 4.4+ but not 4.2.
We would like to see the currently supported MongoDB Server version 4.2 available on the Ubuntu 20.4 LTS distribution.5 votes
- Don't see your idea?