Disk size autoscaling is enabled by default on most services. When you consume 85% or more of your existing disk space, disk size is automatically increased to the next size available, up to a configurable limit.
Autoscaling can only increase disk size, not decrease it. You can have a disk up to 16 TB in size.
Autoscaling can change the disk size once every 6 hours. When the increase is requested, the new limit is applied, and then the used space is optimized. The optimization process does not require downtime, and in most cases it happens very quickly. However, if you have a lot of existing data, optimization can take longer. You should expect 6 to 24 hours of optimization time for every terabyte of data. For more information, see the Amazon Elastic Block Store documentation.
Warning
If you ingest very large amounts of data, autoscaling might not be able to keep up with data ingest. This happens because you need to wait for storage optimization between resizes. In that case, you need to scale your storage manually. To learn more, see the limitations of autoscaling.
You can also use autoscaling with Timescale multi-node clusters. In this case, you should define different scale limits for the access node and data nodes. This is not just because they have different workloads, but also because access nodes are less demanding for storage than data nodes. Data nodes have a single scaling threshold that applies across all the data nodes.
Disk size autoscaling is enabled by default on most services. You can configure autoscaling on your services to work in the most effective way for your workload.
- In the Timescale console, from the
Serviceslist, click the name of the service you want to modify. - In the
Service overviewpage, navigate to theOperationstab, and clickAutoscaling. - Toggle
Enable storage autoscalingto turn autoscaling on or off. - In the
Storage autoscaling limitfield, adjust the slider to set the maximum disk size. Autoscaling can not increase the disk size higher than this limit. - Review the new allocations and costs in the comparison chart.
- Click
Applyto save your changes. The new disk size generally becomes available within a few seconds.
Under very heavy data ingest loads, your data might grow faster than your new storage can be optimized. There must be a gap of at least 6 hours between resizes. For larger databases, there should be a gap of 6 to 24 hours for each terabyte of data.
Refer to the autoscaling size increases to check the next few tiers of storage. If you expect your database to outgrow an upper tier while still optimizing the next tier, you should manually scale your database to your expected final size. This prevents you from outgrowing your data storage before it can be resized again.
For example, say you have 100 GB of storage. The next two tiers are 125 GB and 150 GB. To resize to 125 GB, AWS needs to modify the underlying storage volume. This can typically happen within 6 hours, but it might take 24 hours in some cases. The time doesn't always scale linearly with the volume size. For safety, you might want to leave 24 hours.
Resizing is triggered when your disk is 85% full, so the first resize is triggered at 85 GB, and the second resize is triggered at 118 GB. If you expect your data to grow from 85 GB to 118 GB within a day, you should manually resize your storage to accommodate the heavy load.
Size increases occur with these gradations:
- 10 GB
- 25 GB
- 50 GB
- 75 GB
- 100 GB
- 125 GB
- 150 GB
- 175 GB
- 200 GB
- 225 GB
- 250 GB
- 275 GB
- 300 GB
- 325 GB
- 350 GB
- 375 GB
- 400 GB
- 425 GB
- 450 GB
- 475 GB
- 500 GB
- 600 GB
- 700 GB
- 800 GB
- 900 GB
- 1 TB
- 1.5 TB
- 2 TB
- 2.5 TB
- 3 TB
- 4 TB
- 5 TB
- 6 TB
- 7 TB
- 8 TB
- 9 TB
- 10 TB
- 12 TB
- 14 TB
- 16 TB
Keywords
Found an issue on this page?
Report an issue!