search

bitpoke / mysql-operator

Asynchronous MySQL Replication on Kubernetes using Percona Server and Openark's Orchestrator.
https://www.bitpoke.io/docs/mysql-operator/getting-started/
Apache License 2.0
993 stars 275 forks source link

Labels are not updated on pods #918

Open oau-dev opened 3 months ago

oau-dev commented 3 months ago

hello,

for any reasons the labels on pod are not updated. Sometimes on master and nothing else happend. No switch, and in the UI everything is fine but the cluster is not reachable. 

db-mysql            10.244.13.71:8080,10.244.13.71:3306                                  61d
db-mysql-master     <none>                        61d
db-mysql-replicas   10.244.13.71:8080,10.244.13.71:3306                                 61d
``

Sometimes on replica.

``
db-mysql                 10.244.13.24:3306                                                    61d
db-mysql-master     10.244.13.24:8080,10.244.13.24:3306                                  61d
db-mysql-replicas    <none>                                                               61d

In the operator log I got a lot of logs like this : 


orchestrator-reconciler "msg"="skip set read-only/writable" "key"={"Namespace":"xxxxxxxx","Name":"db"} "instance"={"Hostname":"db-mysql-2.mysql.xxxxxxx","IsUpToDate":"false","MasterHostname":"db-mysql-1.xxxxxx"}
``

I don't understand this logs and I don't know if it's related or important.

Any clue ?