Skip to content

Commit bc444fa

Browse files
Some typo fixing, paraphrasing, etc in the doc
1 parent 2ff5dc7 commit bc444fa

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

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

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This article explains how Horizontal autoscaling works, what the requirements ar
1515
## How does it work
1616

1717
With horizontal autoscaling, additional Hypernodes will be added automatically to your main Hypernode at peak times. The extra Hypernodes will be used as PHP fpm workers.
18-
Since there are no configuration or IP changes needed, Horizontal autoscaling is zero-downtime.
18+
Since there's no configuration or IP changes needed, Horizontal autoscaling has zero-downtime.
1919

2020
For Horizontal autoscaling you can configure some conditions. If the conditions are met from the configured settings in the Control Panel, Horizontal autoscaling will be triggered.
2121
You can configure the following conditions:
@@ -42,21 +42,25 @@ This approach selects the longer duration between user-defined settings or the f
4242

4343
### Downscaling
4444

45-
If the monitor agent noticed if one Hypernode will be removed, the used resources will stay below the configured thresholds, the downscale operation will be triggered.
45+
If the monitor agent notices that the used resources are below the configured thresholds, the downscale operation will begin. This will lead to removing the additional servers that are no longer needed.
46+
4647
Downscale will happen by detaching the autoscaling instances from the main Hypernode one by one.
47-
After a downscale operation has completed, there will be a cooldown of 15 minutes to monitor the behaviour of the newly available resources before downscale again.
48+
After a downscale operation has been completed, there will be a cooldown of 15 minutes to monitor the behaviour of the newly available resources before downscaling again.
49+
4850
If the amount of used resources is still below the configured threshold, another downscale operation will be triggered.
51+
4952
If there is need for extra resources instead, extra resources will be added again.
5053

5154
## Horizontal autoscaling requirements
5255

5356
Horizontal autoscaling is available on all the Falcon cloud plans (OpenStack).
57+
5458
Next to the provider, horizontal autoscaling does have a couple of additional requirements.
5559

5660
### Supported CMS
5761

5862
Horizontal autoscaling is available for Magento2.
59-
To make use of Horizontal autoscaling, there are a couple of other requirements the Hypernode and the application should met:
63+
To make use of Horizontal autoscaling, there are a couple of other requirements the Hypernode and the application should meet:
6064

6165
### Operating system
6266

@@ -136,7 +140,7 @@ More information about [Elasticsearch o Hypernode](../../hypernode-platform/tool
136140
Please make sure RabbitMQ host is set to `rabbitmqmaster` in the Magento2 configuration file at `<magento_root>/app/etc/env.php`
137141
More information about [RabbitMQ o Hypernode](../../best-practices/database/how-to-run-rabbitmq-on-hypernode.md)
138142

139-
### Make sure we use MySQL 5.7 or higher
143+
### Make sure to use MySQL 5.7 or higher
140144

141145
The configured MySQL version should be 5.7 or above. You can check the enabled MySQL version by running the following command.
142146

@@ -150,9 +154,10 @@ Example output if MySQL version is 8.0:
150154
mysql_version is set to value 8.0
151155
```
152156

153-
If your MySQL version is still set to 5.6, you can concider [upgrade](../mysql/how-to-use-mysql-on-hypernode.md) the MySQL version to a supported version for autoscaling.
157+
If your MySQL version is still set to 5.6, you can consider [upgrading](../mysql/how-to-use-mysql-on-hypernode.md) the MySQL version to a supported version for autoscaling.
154158

155159
After the version validation, please verify the MySQL host is set to `mysqlmaster`. You can verify this by running `cat app/etc/env.php | grep -i mysql | grep -i host` from the magento root.
160+
156161
You should see something similar to `'host' => 'mysqlmaster',`. If this is not the case please make sure the database connection host is set to `mysqlmaster` instead of `localhost` or `127.0.0.1` in the magento configuration file at `<magento_root>/app/etc/env.php`.
157162

158163
### Make sure the Hypernode is a production plan
@@ -161,4 +166,4 @@ Unfortunately we don't support Horizontal autoscaling for development plans.
161166

162167
## Enabling Horizontal Autoscaling
163168

164-
For detailed steps on enabling horizontal Autoscaling, please refer to our documentation: [How to enable vertical Autoscaling?](how-to-enable-vertical-autoscaling.md)
169+
For detailed steps on enabling horizontal Autoscaling, please refer to our documentation: [How to enable Horizontal Autoscaling?](how-to-enable-horizontal-autoscaling.md)

0 commit comments

Comments
 (0)