Yandex StoreDoc release notes
March 2026
- Added the
--redactClientLogDataoption to mask client request data before it is written to logs. This option hides the content of messages associated with events but keeps technical metadata (error codes, line numbers, file names). - If a Yandex StoreDoc replica is far behind, the service can now use backup recovery tools to update its data faster and without placing additional load on the master host.
- Added separate roles to view and edit (reschedule) maintenance without access to the cluster.
January 2026
- Added the Shards tab to Monitoring. From this tab, you can track metrics for each individual shard and promptly detect problematic nodes.
- Added the option of partial Yandex StoreDoc cluster recovery from a backup. You can restore specific databases or collections by adding them to include or exclude lists.
December 2025
- Added detailed metrics for disk usage on cluster hosts.
- Added execution details for operations on the cluster.
- All new clusters are created with a Connection Manager connection by default.
November 2025
Added the managed-mongodb.restorer role for restoring clusters from backups. To learn more, see Access management.
October 2025
- Added integration with Connection Manager. This tool allows you to connect to databases without exposing your password, reducing the risk of it being compromised.
- Added support for configuring the maximum number of connections and other cluster settings via API.
- Simplified resetting values to defaults via API: now you can update settings by passing just the field name, without specifying a value.
- Added a new status in the management console for cluster hosts being restored from a backup.
- Added support for manually configuring the chunk size in sharded clusters.
- Added support for managing data migration during shard addition or removal via
rangeDeleterBatchSize,rangeDeleterBatchDelayMS, andmigrateCloneInsertionBatchSizesettings. - Added SRV records for improved host FQDN stability. Connections now use the following format:
mongodb+srv://[username: password@]<cluster_ID>.mdb.yandexcloud.net[/[defaultauthdb][? options]]. - Complete replica configuration details are now displayed in the management console and in the
yc managed-mongodb host listCLI command output. - Added new host classes on AMD Zen 4 and AMD Zen 4 HighFreq platforms.
July 2025
- Added support for encrypting storage disks with a custom KMS key during cluster creation or when restoring it from a backup.
- Switched to the Yandex StoreDoc DBMS compatible with the relevant MongoDB versions.
April 2025
- Added support for MongoDB 8.0. To learn how to update your cluster to the latest version, see Yandex StoreDoc version upgrade.
- Added support for restoring sharded clusters from backups.
March 2025
Added support for connecting to a cluster database via Yandex WebSQL.
December 2024
Starting December 2, 2024, you can no longer create clusters with MongoDB version 5.0, as support for this version was discontinued by the vendor.
October 2024
Added support for setting a retention period for automatic backups.
September 2024
Added support for MongoDB version 7.0. To learn how to update your cluster to the latest version, see Yandex StoreDoc version upgrade.
February 2024
Added support for the flowControl, changeStreamOptions, net.compression.compressors, and storage.wiredTiger.indexConfig.prefixCompression settings.
Q1 2023
Added support for creating sharded clusters directly, without having to create an unsharded cluster first and then shard it.
Q4 2022
- Added support for MongoDB version 6.0. To learn how to update a cluster to the latest version, see Yandex StoreDoc version upgrade.
- Increased the maximum storage capacity for clusters:
- Based on network HDDs and SSDs: 1024 GB → 2048 GB
- Based on non-replicated SSDs: 1024 GB → 2232 GB
- Based on local SSDs: 1024 GB → 1500 GB
Q3 2022
Added access to the oplog collection for users with the mdbReplication role.
Q2 2022
- Existing MongoDB 4.0 clusters have been upgraded to version 4.2.
- The storage resizing process has been accelerated by accounting for ZooKeeper lock specifics.
- Identified an issue when restoring a version 5.0 cluster from a backup. A fix is expected in future MongoDB 5.0 releases.
Q1 2022
Support for MongoDB version 4.0 has ended. You can no longer create clusters with this version. Existing MongoDB 4.0 clusters will be automatically upgraded to version 4.2.