Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

Feedback

add IO throughput related fields to 'serverStatus' output

There is no IO throughput related fields in the result of serverStatus, instead in FTDC this is available in the disk metrics. Need it in `serverStatus` output so that we can monitor it.
Guest almost 3 years ago in Storage & Transactions 1 Submitted

Restore Backup Snapshots to Sharded Clusters via mongos

Migrating large sharded clusters to a different cluster pre-sharded with different shard keys requires a significant amount of time to balance post-restore. This is a feature request to restore a snapshot on a per document basis through a mongos....
Guest over 5 years ago in Backup & Restore 0 Submitted

we have an ask to use 4 in snapshotIntervalHours

For the api - https://www.mongodb.com/docs/ops-manager/current/reference/api/backup/update-one-snapshot-schedule-by-cluster-id/ we have an ask to use 4 in snapshotIntervalHours. Right now its not supported. Supported ones are - 6, 8, 12, or 24. P...
Guest about 1 year ago in Backup & Restore 0 Submitted

In the event of an integrity check job failure, an alert should be shown on Ops manager UI instead of solely relying on email

Integrity Check Jobs failures get emailed to the configured "mms.backup.alertsEmailAddr" address and logged in daemon.log. This information should also be available in Ops Manager UI so that the user can quickly check before trying any restoration.
Guest about 6 years ago in Backup & Restore 0 Submitted

Automatically move HEADS in case of backup daemon problem

In configuration with multiply daemons in case of daemon problem (down) switch to another one automatically with restart backup upon need.
Ilya Shifman about 1 year ago in Backup & Restore 0 Submitted

Enable BigInt Support for Blockchain Use

Smart contracts on Ethereum and on Ethereum compatible chains are represented as 256bit integers. There are several libraries widely used to deal with these data types in JavaScript such as bn.js and BigNumber.js. A potential workaround could be...
Guest over 3 years ago in Storage & Transactions 0 Submitted

Allow changing compression of an existing collection

I'd like to switch my database from Snappy to Zstd compression. Currently, it doesn't seem that it is possible to change the compression of an existing collection. It would be nice if there were a way to do this, even if (for example) it requi...
Guest almost 4 years ago in Storage & Transactions 0 Submitted

wired

wiredTiger open files usage Currently WT uses a file per collection and index, leading in some scenarios to extremely high number of open files/dhandles. Is there any plan to support one file/dhandle per database?
Guest over 5 years ago in Storage & Transactions 0 Submitted

Cascading delete for DBRefs

Since transactions have been added in 2018, which work across collections (https://www.mongodb.com/docs/manual/core/transactions/) and across shards (https://www.mongodb.com/docs/manual/core/transactions-sharded-clusters/), shouldn't cascading del...
Guest almost 3 years ago in Storage & Transactions 0 Submitted

Easier way to troubleshoot storage use size discrepancy across nodes in the same replica set

While initial sync may potentially help on this topic, it would be great if the product has any easier way to identify the cause of significantly different storage use size (so to give a better confidence if initial sync is going to help).
Ka Lung Ng over 1 year ago in Storage & Transactions 0 Submitted