Yandex StoreDoc release notes
July 2025
- Now you can encrypt storage disks with a custom KMS key when creating a cluster and 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 a cluster to the latest version, see Upgrading Yandex StoreDoc version.
- You can now restore a cluster with enabled sharding from a backup.
March 2025
You can now connect to a cluster database via Yandex WebSQL.
December 2024
Starting December 2, 2024, you can no longer create MongoDB 5.0 clusters: the version was discontinued by the vendor.
October 2024
Now you can specify a retention period for your automatic backups.
September 2024
Added support for MongoDB version 7.0. To learn how to update a cluster to the latest version, see Upgrading Yandex StoreDoc version.
February 2024
The flowControl, changeStreamOptions, net.compression.compressors, and storage.wiredTiger.indexConfig.prefixCompression settings are now supported.
Q1 2023
You can now create a sharded cluster instead of first creating a non-sharded one and then splitting it into shards.
Q4 2022
- MongoDB 6.0 is now supported. To learn how to update a cluster to the latest version, see Upgrading Yandex StoreDoc version.
- Increased maximum storage capacity for cluster:
- 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
- Updated existing MongoDB 4.0 clusters to version 4.2.
- Accelerated the process of changing storage size considering ZooKeeper lock specifics.
- Detected an issue when restoring a version 5.0 cluster from a backup. A fix is expected in the new MongoDB 5.0 releases.
Q1 2022
MongoDB 4.0 is no longer supported. Clusters cannot be created with this version. Existing MongoDB 4.0 clusters will be automatically updated to version 4.2.