Scale disk storage for your Aiven for Grafana® service
Scale the disk storage of your Aiven for Grafana® service up or down without disrupting the running service.
Adding or removing disk storage does not disrupt the running service. You pay only for extra storage instead of upgrading compute resources.
You can add extra storage when you create a service or after it is running. When you add storage to a running service, the Aiven Platform provisions the extra disk and adds it to the running instances.
For a clustered service such as Aiven for Apache Kafka®, Aiven divides extra storage equally between the nodes. For a shared service, each node receives the full extra capacity.
Limitations
- Disk added for extra storage is slower than the original disk until the next maintenance update. The slower disk can reduce performance for I/O-intensive workloads.
- Maximum storage depends on the plan, service type, and cloud provider. It can be up to five times the plan's base storage size.
- Cloud providers limit how many times you can increase storage between maintenance updates. If you reach the limit, run a maintenance update to optimize performance.
- You cannot add storage during a maintenance update.
- Dynamic disk sizing (DDS) is not supported on custom service plans.
If you add storage when you create a service, Additional disk storage shows an estimated monthly cost. The Service summary lists plan storage plus additional storage. The estimated monthly price includes the additional storage cost.
If you add storage to a running service, the Aiven Console shows the cost of the additional storage and related backups. The same costs appear on your invoices.
Add or remove storage
Add storage when you create a service
To add storage while you create a service:
- In Additional disk storage, set the size with the slider or enter a value in GB.
- Review the estimated monthly cost.
- In the Service summary, click Create service.
Change additional storage later on the running service, or enable automatic disk scaling with Aiven Autoscaler.
Change storage on a running service
You cannot add or remove storage when service nodes are in the rebuilding state, for example during a maintenance update or a service upgrade.
If you are removing disk storage:
- Make sure the data in your service does not exceed the allocated storage. If it does, you cannot remove the additional storage.
- Plan for the time it takes to rebuild the service. The time depends on the service.
- Console
- CLI
- Terraform
-
In your service, click Service settings.
-
In the Service plan section, click Actions > Manage additional storage.
-
Change the disk storage.
note-
The price shown for the additional storage includes backup costs.
-
You can only remove storage that you previously added using this feature. To downgrade further, you can change your service plan.
-
-
Click Save Changes.
Use Aiven CLI to add or remove additional storage using
avn service update with the
--disk-space-gib flag to specify the total disk space to provide to your service.
For example, if your service has a 80-GiB disk and you would like to add an extra 10-GiB disk, use:
avn service update --disk-space-gib 90 --project PROJECT_NAME SERVICE_NAME
-
When you perform a horizontal service upgrade or downgrade, remember to include all additional disks the service uses.
For example, when switching from
Startup-4toBusiness-4or fromBusiness-4toStartup-4, include all the additional disks available for this service. -
When you fork an existing service, include all additional disks the service uses.
Use the additional_disk_space attribute in
your Aiven service resource.
If you added storage, the additional storage is available immediately. If you removed additional storage, the service nodes go through a rolling restart. Depending on the service type and configuration, there might be a short downtime for services with no HA capabilities.
Storage optimization is performed at the next maintenance update after a change to the storage size. Due to cloud provider limitations, there is a limit on how many times storage can be increased between two maintenance updates. When this limit is reached, perform a maintenance update for performance optimization. Plan increases to avoid reaching this limit.
Related pages