Database Auto-Configuration
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use Database Auto-Configuration 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.
Ruk-Com Cloud PaaSSmart Auto-Configurationwill changeMySQL, MariaDB, andPerconadatabases automatically according to the resource limits allocated to the container. That is, changes specifically affect the configuration of the /etc/my.cnf file and the following settings:
- key_buffer_size
- table_open_cache
- myisam_sort_buffer_size
- innodb_buffer_pool_size
Starting with versions 5.7 and 8.0 ofMySQL/PerconaandMariaDB10.x Two additional parameters are defined:
- innodb_buffer_pool_instances- Deprecated in MariaDB since 10.6.x (always had 1 instance pool).
- innodb_buffer_pool_chunk_size
If you want to manually change the settings from the list above, You must setenvironment variablesJELASTIC_AUTOCONFIGto "false", "disable" or "0" or your custom changes will be overwritten.
Tips:Alternatively, you can override the settings in the file./etc/my.cnf(including settings managed by Smart Auto-Configuration) specified in the file/etc/mysql/conf.d/custom.cnf
original use
If you want to change the settings that were automatically configured in the old container. You must delete “#Jelastic autoconfiguration mark.” at the beginning of the file./etc/my.cnf
