openstack/kolla-ansible.git/ansible/roles/loadbalancer/templates/proxysql/proxysql.yaml.j2, branch stable/2026.1

Fix ProxySQL not using backup writer node for reads

2026-09-17T06:38:11+00:00

Set writer_is_also_reader to 2 in the Galera hostgroup configuration so that the backup writer node also serves reads, instead of sitting idle while all read traffic went to the single remaining reader node. The writer node is never added to the reader hostgroup regardless of this setting, only the backup writer is affected. See bug report for performance difference details. Closes-Bug: #2167037 Change-Id: Ib5145c200c3cd70f861824abd967748faf61e1cf Signed-off-by: fprzewozn (cherry picked from commit 42eec877ff572fd724af8a1c0fa64acf5e824c7b)

Switch to pypi version of j2lint and fix linting errors

2025-12-30T16:31:17+00:00

Since ipwrap filter is getting moved another time inside ansible code - let's switch to j2lint that is actively maintained and it's rules will help in readability of jinja2 templates Change-Id: I6762b691b927de31fa1abd83c4c14e87226fe5e2 Signed-off-by: Michal Nasiadka

proxysql: Add support for mysql-verbose_query_error

2025-05-20T13:58:03+00:00

Default value is taken from openstack_logging_debug Change-Id: I18d3ecac6e3d92029b12b3f9d6f27e3e6579a8c7

proxysql: Revert to upstream defaults for most settings

2025-01-20T10:49:17+00:00

Add options to configure those settings that were hardcoded Stop Kolla-Ansible from owning those defaults Change-Id: I33dd9b626e85ace41807f2f2b83452c6b8491a0f

proxysql: Add mariadb_monitor_read_only_interval

2024-12-16T14:17:31+00:00

It's needed to be configured on environments like our CI, because of low cpu/network resources proxysql marks healthy nodes as OFFLINE_HARD Change-Id: I6d1e9e77abc48d82ffd6ade33997c83bb601b0eb

Add backend TLS between MariaDB and ProxySQL

2024-10-25T14:38:39+00:00

This commit adds TLS connection between ProxySQL and MariaDB. Frontend TLS ( between services and ProxySQL) will be added in another commit. Parialy Implements: mariadb-ssl-support Change-Id: I154cbb096469c5515c9d8156c2c1c5dd07b95849 Signed-off-by: Matus Jenca

Adjust ProxySQL shunning behavior for single-node clusters

2024-10-17T12:37:32+00:00

In single-node clusters, ProxySQL shuns the server on MySQL errors, causing failures during upgrades or container restarts. This change increases the timeout to 10 seconds, allowing the backend time to recover and preventing immediate errors in CI environments. Change-Id: I70becdc3fcb4ca8f7ae31d26097d95bdc6dd67eb

Merge "Updating proxysql.yaml.j2 to use mariadb_port for backends"

2024-10-02T16:45:38+00:00

Improvement of ProxySQL Monitoring Configuration

2024-09-23T13:38:10+00:00

This update enhances the monitoring of the databasecluster in ProxySQL. The default monitoring intervals were insufficient for reliably detecting failures in the Galera cluster environment. A detailed configuration for monitoring intervals has been introduced, providing better control over how quickly and accurately ProxySQL can identify issues. - Variables such as `mariadb_monitor_connect_interval`, `mariadb_monitor_galera_healthcheck_interval, and `mariadb_monitor_ping_interval` significantly reduce the time between connection checks. - Timeouts like `mariadb_monitor_galera_healthcheck_timeout` and `mariadb_monitor_ping_timeout` allow faster failure detection, while `mariadb_monitor_galera_healthcheck_max_timeout_count` sets the maximum number of allowed timeouts before marking a node as down. Calculation: - Galera healthcheck: 4 seconds (interval) + 1 second (timeout) + 4 seconds (interval) + 1 second (timeout) = 10 seconds. - Ping healthcheck: 3 seconds (interval) + 2 seconds (timeout) + 3 seconds (interval) + 2 seconds (timeout) = 10 seconds. Both the health check and ping check mechanisms will detect a node failure within a maximum of 10 seconds. Both processes (health check and ping) operate independently, and failure in either mechanism will mark the node as failed. Health Check Failure Detection: Up to 10 seconds. Ping Failure Detection: Up to 10 seconds. Connect Attempts: ProxySQL also tries to connect every 2 seconds, which helps monitor connectivity. These changes ensure that ProxySQL can detect issues in 10 seconds as haproxy, significantly reducing downtime compared to default settings. This adjustment enables faster and more reliable monitoring, improving system stability and reducing potential downtime in production environments. Change-Id: Ic28801519cdb35ed2387a1468b9df661847a5476

Fix IPv6 address format in ProxySQL configuration

2024-09-20T16:51:19+00:00

This patch resolves an issue where ProxySQL could not bind due to incorrectly formatted IPv6 addresses in the `mysql_ifaces` configuration. The kolla's `put_address_in_context` filter is now used, ensuring the addresses are properly enclosed in square brackets for correct binding. Closes-Bug: #2081106 Change-Id: Ic166b8d9a500023c8d23ec9fee03b28b268b26e7