Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
I can see strange behaviour in our PXC operator in case of HaProxy deployment. It can't set correct status:
❯ kubectl get pxc
NAME ENDPOINT STATUS PXC PROXYSQL HAPROXY AGE
haproxy haproxy-haproxy.haproxy-19743 initializing 3 3 9m24s
Everything is ok with cluster but we see 'initializing' state. The root of the issue is that in haproxy test we test a lot of different cases e.g. kill current primary to be sure that all haproxy pods will forward traffic to a new one. And it seems from time to time the connection to DB from operator hangs and the status can't be updated. So, we need to set timeout for such connections to fix it.
Hi,
I can see strange behaviour in our PXC operator in case of HaProxy deployment. It can't set correct status:
❯ kubectl get pxc NAME ENDPOINT STATUS PXC PROXYSQL HAPROXY AGE haproxy haproxy-haproxy.haproxy-19743 initializing 3 3 9m24sEverything is ok with cluster but we see 'initializing' state. The root of the issue is that in haproxy test we test a lot of different cases e.g. kill current primary to be sure that all haproxy pods will forward traffic to a new one. And it seems from time to time the connection to DB from operator hangs and the status can't be updated. So, we need to set timeout for such connections to fix it.