Auto-Configuration Overview

Smart Auto-Configuration of Containers

Smart Auto-Configuration automatically adjusts selected managed software stacks according to the container’s Cloudlet scaling limit, helping the platform use available RAM and CPU resources more efficiently.
On this page

Supported Templates

Smart Auto-Configuration is available for selected certified stacks:

Databases MySQL, MariaDB, and Percona.
LiteSpeed LiteSpeed Web Server, LiteSpeed Web ADC, and LLSMP.
Apache PHP and NGINX PHP stacks use the older PHP auto-configuration implementation rather than the modern Smart Auto-Configuration mechanism.

How Smart Auto-Configuration Works

  • Supported templates use the modern systemd initialisation system required by the auto-configuration mechanism.
  • The JELASTIC_AUTOCONFIG environment variable controls whether the feature is active.
  • The default value is true, so Smart Auto-Configuration is enabled automatically.
  • Configuration values are calculated according to the container’s Cloudlet scaling limit.

Enable or Disable Auto-Configuration

To disable Smart Auto-Configuration, add or edit the JELASTIC_AUTOCONFIG variable through the dashboard and set its value to false.

JELASTIC_AUTOCONFIG environment variable
Set JELASTIC_AUTOCONFIG to false to disable Smart Auto-Configuration.
Apply changes: Restart the affected node or nodes after changing the JELASTIC_AUTOCONFIG value.

Smart Recovery after OOM

For supported database containers, Smart Auto-Configuration can also react to Out-of-Memory events. When the OOM killer terminates a critical process and makes the database container inoperable, the platform restarts the node and reduces the default memory allocation.

The recovery mechanism decreases the innodb_buffer_pool_size value. When another OOM restart occurs, the reduction cycle is repeated until the configured maximum number of cycles is reached.

Smart OOM recovery works only when JELASTIC_AUTOCONFIG is enabled.

The documented database versions supporting this recovery mechanism include:

DatabaseSupported Versions
MySQL8.0.26 and 5.7.35
MariaDB10.3.30, 10.4.20, 10.5.11, and 10.6.3
Percona5.7.33 and 8.0.23

OOM Recovery Variables

The following environment variables control the OOM recovery behaviour:

VariablePurposeDefault
OOM_DETECTION_DELTA Defines how long the platform analyses /var/log/messages after a service restart to determine whether the OOM killer caused it. 2 seconds
OOM_ADJUSTMENT Defines how much innodb_buffer_pool_size is reduced after each OOM-related restart. The value may be specified as a percentage, MB, or GB. 10%
MAX_OOM_REDUCE_CYCLES Sets the maximum number of automatic buffer-pool reduction cycles. 5 cycles
OOM recovery environment variables
Environment variables used to control automatic OOM recovery.
Reset recovery adjustments: Increase the container’s Cloudlet limit to reset the automatic memory reductions introduced by OOM recovery.

What’s next?