There is a script "/usr/local/bin/check_pxc.sh" calling from the haproxy configuration file - "/etc/haproxy/haproxy.cfg" which monitors the database and generates frequent health check logs.

To control this, we have tried to change the Haproxy config via "cr.yaml"; however it's still appearing the same events irrespective of the change. We have tried with different modes such as "err" & "info"; however, the same result.

cr.yaml

configuration: |
      global
        maxconn 2048
        external-check
        log stdout  format raw  local0  emerg
        stats socket /etc/haproxy/pxc/haproxy.sock mode 600 expose-fd listeners level admin

      defaults
          log global
          option  tcplog
          option dontlog-normal
          mode tcp
          retries 10
          timeout client 28800s
          timeout connect 100500
          timeout server 28800s

 

cr.yaml

configuration: |
     global
         maxconn 2048
         external-check
         log stdout  format raw  local0  emerg
         quiet

kubectl logs cluster1-haproxy-1 -f

The following values are used for PXC node 10.112.2.11 in backend galera-replica-nodes:
wsrep_local_state is 4; pxc_maint_mod is DISABLED; wsrep_cluster_status is Primary; 3 nodes are available
PXC node 10.112.2.11 for backend galera-replica-nodes is ok

It would be nice if we could control or fix this behaviour which avoids continuous logging and DB interaction.