Smart Auto-Configuration of Containers

Objective

This guide explains how to use Smart Auto-Configuration of Containers on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

In order to ensure efficient use of resources, Ruk-Com Cloud can automatically configure some stack management values according to scaling limits (according to the number of cloudlets) Currently, the following templates can take advantage of the feature.Smart Auto-Configuration:

• Databases:MySQL, MariaDB, Percona
• PHP:Apache, NGINX
• LiteSpeed: Web Server,ADC,LLSMP

Tips:Click the links to see what settings can be adjusted in each case.

The above-mentioned stack has some characteristics that support its use:

1. The template uses a modern systemd default program that provides many of the features and tools needed to use automatic configuration.

2.VariablespecialJELASTIC_AUTOCONFIGenvironment determines whether the auto-configuration feature should be enabled (true by default) or disabled (false).

If you want to disable Smart Auto-Configuration, add (or edit if it already exists) this variable with a value of false via dashboard.

Don't forgetRestartNode(s) to deploy changes

3. Intelligent recovery after OOM errors allows automatic configuration to be re-adjusted to reduce container memory usage.

More: Smart OOM recoveryRun on enabled containers JELASTIC_AUTOCONFIG and currently only for the following database stacks

-MySQL 8.0.25; 5.7.34
-MariaDB 10.3.30; 10.4.20; 10.5.11; 10.6.3
-Percona 5.7.33; 8.0.23

If doingOOM killerMake the container unusable. (Because some important processes are destroyed) it will automatically restart this load and Smart Recovery will lower the parameters.innodb_buffer_pool_sizeIn case the incident happens again The reduction cycle will be repeated.

You can customizeenvironment variablesTo adjust system behavior related to the OOM Kills issue:

• OOM_DETECTION_DELTA- Set a time interval (default 2 seconds) to analyze and record. /var/log/messages After restarting each service to determine if it was caused by the OOM killer or not.
  
• OOM_ADJUSTMENT- Set values to %, MB, GB (default 10%) where parameters innodb_buffer_pool_size The current should decrease after each restart caused by OOM.
  
• MAX_OOM_REDUCE_CYCLES- Set the maximum number of cycles for size reduction. innodb_buffer_pool_size (default 5 times)