How to change a cluster's resources
This guide explains how to adjust an existing MongoDB cluster from the Hikube console: disk size, version and external access.
Prerequisites
- An existing MongoDB cluster in your project
- Sufficient project quotas for the new configuration
What can be changed
| Parameter | Can be changed after creation |
|---|---|
| MongoDB Version | Yes, to a higher version only |
| Disk size (GB) | Yes, upwards only |
| External access | Yes |
| Preset | No, "The resources preset cannot be changed after creation" |
| Number of replicas | No, "The mode cannot be changed after creation" |
| Sharding | No, the option is not in the edit form |
To change the preset, the number of replicas or the topology of an existing cluster, contact support.
Steps
1. Open the edit form
- Open DB & Messaging → MongoDB.
- Open the cluster, then click Edit (or use Actions → Edit in the list).
The Edit MongoDB cluster page shows the Cluster settings card and the impact on the project quotas.
2. Adjust the settings
- Disk size (GB): enter the new capacity, at least equal to the current size. A lower value displays "The disk size cannot be reduced: N GB minimum." and is not saved.
- MongoDB Version: select the target version. The form only offers the current version and the higher versions.
- External access: enable or disable exposure on the public Internet.
MongoDB only supports major version upgrades from one version to the next (6.0 → 7.0 → 8.0). The form offers all higher versions, including a version jump: do not skip a version.
When you change the version, the warning "The cluster instances will restart" is displayed: the change restarts the cluster instances as soon as you save, and an upgraded version cannot be downgraded. Plan it outside peak hours.
3. Save
Click Save. The "Cluster updated" message confirms the change. If the new configuration exceeds the project quotas, the button stays disabled.
The API applies the same rules: a version lower than the current one is refused with code 150203, a disk size smaller than the current one with code 150204.
Verification
The cluster page shows the new values in the MongoDB Version and Allocated Size cards. From mongosh, check the space used:
db.stats({ scale: 1024 * 1024 })
Further reading
- MongoDB concepts: replication, presets, network access
- Configure sharding