Skip to content

Commit a55cce7

Browse files
committed
fix header hierarchy
1 parent 10a8bcf commit a55cce7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/hypernode-platform/autoscaling/how-does-autoscaling-work.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Vertical autoscaling is triggered once the conditions are met from the configure
1515
- **CPU Load Threshold:** CPU load that is continuously monitored by the autoscaling agent. The percentage value you see is the actual load divided by the number of CPUs you have. For example, if your actual load is 2, but you have 4 CPUs, your CPU load percentage is 50%. The default setting is 70%.
1616
- **Minimum Duration in Minutes:** Minimum amount of time the server is overloaded before autoscaling gets triggered. We monitor your CPU load every minute; autoscaling will be triggered once the CPU load condition is met for the minimum amount of time set in the Control Panel. The default setting is 15 minutes.
1717

18-
### Autoscaling workflow
18+
## Autoscaling workflow
1919
To minimize downtime during the process, we employ a live volume swapping method. We install a new Hypernode without copying the data over the network to the new hosting environment. Next, we detach the volume using the API and mount it on the new machine before adjusting the DNS.
2020

2121
The feature is available on the cloud plans (OpenStack and AWS).

0 commit comments

Comments
 (0)