Skip to content

Commit ea2c5f2

Browse files
committed
mdformat
1 parent a55cce7 commit ea2c5f2

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

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

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,24 +16,29 @@ Vertical autoscaling is triggered once the conditions are met from the configure
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

1818
## Autoscaling workflow
19+
1920
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.
2021

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

2324
## Autoscaling process
25+
2426
Once set conditions are met and autoscaling is triggered, you get upgraded to the next available plan for 24 hours. When your Hypernode is in the boosted state, you can still adjust the settings, but you cannot change your plan. If you wish to do so, please contact support@hypernode.com.
2527

2628
If the server remains overloaded post-autoscaling, the next autoscaling trigger is determined based on these criteria.
2729
The greater of either:
30+
2831
- User-defined minimum duration for CPU threshold surpassing: Allows time to assess newly allocated resources' impact on CPU performance.
2932
- A cooldown period of 15 minutes: Ensures a minimum interval for reassessment when the user-defined duration is less than 15 minutes.
3033

3134
This approach selects the longer duration between user-defined settings or the fallback duration before initiating the next autoscaling event. It ensures adequate time for evaluating resource changes on CPU performance. Autoscaling is capped at the biggest plan available on each cloud provider.
3235

3336
### How to halt continued Autoscaling
34-
Simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action.
37+
38+
Simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action.
3539

3640
### Returning to the Initial Plan After 24 Hours
41+
3742
Regardless of the number of times your Hypernode was autoscaled, you will go back to your initial plan after 24 hours from your initial upgrade.
3843

3944
## Enabling Autoscaling

0 commit comments

Comments
 (0)