AutoScaling Configurations
Datafy AutoScaler manages your volumes using a set of configurable parameters that control when and how volumes grow and shrink. Datafy's defaults are designed to work well for most workloads, but you can fine-tune behavior per account, per cluster, or per instance through the Configuration page.
For an overview of the grow and shrink lifecycle, see How AutoScaler Works.
Configuration Levels
Configurations follow a four-level hierarchy. Each level inherits from the level above it, and any value set at a lower level overrides the inherited one.
Organization level — applies to every account in the organization.
Account level — applies to every instance in the account. Overrides the organization value.
Cluster level — applies to every instance in a Kubernetes cluster. Overrides the account value.
Instance level — applies to a single instance. Overrides the cluster value, or the account value when the instance is not part of a cluster.
If an override is reverted, the value goes back to inheriting from the level above, and if that inherited value changes later, the override location automatically picks up the new value.
Organization-level configurations can only be set from the organization view. Account, cluster, and instance overrides can be set from either the organization view or the relevant account view.
Viewing and Editing Configurations
You can access the Configurations page by selecting Settings → Configurations in the left sidebar. The navigation tree on the left shows the configuration hierarchy: the organization at the top (when accessed from the organization view), each account below it, and the clusters and instances that have overrides. Select an item to view its values on the right.
Each field shows the current value, the default or inherited value below it, and a Default or Revert indicator showing whether it has been overridden. An inherited value names the level it comes from, for example Inherited from cluster. Click any value to edit it inline - input is validated against the allowed range in real time. Click Save to apply your changes. To restore a single field to the default or inherited value indicated below it, click Revert next to that field. To restore all fields at once, click Revert all to default at the bottom of the page.
To create a new override, click Add New Configuration and pick a level from the tree, which lists every account, cluster, and instance rather than only those that already have overrides. Search to narrow the tree by cluster or instance name. Items that already have custom values are labeled Overridden. Any fields you don't change will continue to inherit from the level above.
Configuration Reference
The tables below describe each configurable parameter grouped by the autoscaling operation they affect. For more on how these operations work, see How AutoScaler Works.
Autoscaling Activation Configurations
These configurations control the initial autoscaling activation of a volume, how the first managed volume is sized and how the initial data copy is performed.
Autoscaling Size Factor
When autoscaling is activated, the initial managed volume size will be at least this factor multiplied by the current used data. A higher value means more free space after activation.
1.3
1.1 – 2.0
Autoscaling Minimum Size (GiB)
The smallest absolute size an autoscaling volume can reach following initial activation. Even if actual usage is lower, the volume will not be sized below this value.
Volumes with original sizes smaller than this cannot be autoscaled.
50 GiB
20 – 16,384 GiB
Autoscaling Minimum Size (%)
The smallest size an autoscaling volume can reach following initial activation, as a percentage of the original volume size. Works alongside the absolute minimum, whichever produces a larger size applies.
10%
5 – 100%
Autoscaling Maximum Size (GiB)
The maximum original volume size eligible for autoscaling. Volumes larger than this will not be autoscaled.
16,384 GiB
Up to 16,384 GiB
Growth Configurations
These control automatic volume growth - when and by how much AutoScaler expands a managed volume as it fills up.
Grow Factor
When a grow is triggered, the new volume size will be this factor multiplied by the current size. Higher values add more headroom per grow but temporarily use more storage.
1.5
Min 1.1
Grow Minimum Free Space
An absolute free-space floor. Growth is triggered when free space on the volume drops below this value. Acts as a safety net to ensure volumes don't run out of space.
5 GiB
Min 5 GiB
Shrink Configurations
These control automatic volume shrinking - when and by how much Datafy reduces a volume to reclaim unused capacity and reduce costs.
Shrink Threshold (%)
If not in shrink cooldown (see below), a shrink is triggered when the volume's utilization falls below this percentage (of the volume's current size). For example, at 50%, a volume using only 30 GiB out of a current size of 65 GiB will shrink.
50%
0 – 75%
Shrink Abort Threshold (%)
If a shrink is already in progress and the expected utilization in the new smaller size rises above this percentage, the shrink is aborted.
85%
80 – 100%
Shrink Size Factor
When shrinking, the new volume size will be at least this factor multiplied by the current used data, ensuring headroom remains after the operation.
1.3
Min 1.1
Shrink Minimum Size (GiB)
The smallest absolute size a volume can be shrunk to. Even if actual usage is lower, the volume will not be sized below this value.
50 GiB
20 – 16,384 GiB
Shrink Minimum Size (%)
The smallest size a volume can be shrunk to, as a percentage of the original volume size. Works alongside the absolute minimum, whichever produces a larger size applies.
10%
5 – 100%
Shrink Cooldown Time
Minimum wait time after any autoscaling operation (activation, grow, or shrink) before a new shrink can be triggered. Prevents rapid grow/shrink cycling on volumes with fluctuating usage.
60 min
Min 1 min
Last updated
Was this helpful?