Skip to content
Snippets Groups Projects
  1. Jan 08, 2025
  2. Oct 25, 2024
  3. Oct 17, 2024
    • Michal Arbet's avatar
      Adjust ProxySQL shunning behavior for single-node clusters · dafac823
      Michal Arbet authored
      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
      dafac823
  4. Sep 23, 2024
    • Michal Arbet's avatar
      Improvement of ProxySQL Monitoring Configuration · 79897566
      Michal Arbet authored
      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
      79897566
  5. Sep 20, 2024
    • Michal Arbet's avatar
      Fix IPv6 address format in ProxySQL configuration · 12eeccdd
      Michal Arbet authored
      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
      12eeccdd
  6. Sep 17, 2024
  7. Jun 21, 2023
  8. Oct 20, 2022
    • Michal Arbet's avatar
      Adds ability to configure ProxySQL's max replication lag · bee253e3
      Michal Arbet authored
      By default ProxySQL's default value of max_replication_lag
      is 0 which is in fact disabling this feature [1].
      If it is greater than 0, ProxySQL will regularly monitor
      replication lag and if it goes beyond the configured threshold
      it will temporary shun the host until replication catches up.
      
      This should be configurable via kolla-ansible as every
      openstack deployment can be different in terms of network
      delays, database load etc.. , so user should have option
      to configure when database backend will be shunned.
      
      [1] https://proxysql.com/documentation/main-runtime/
      
      Change-Id: I66171638abc712cb84b380042f1d29f54c499e73
      bee253e3
  9. Jul 29, 2022
Loading