A MySQL pod can be Running even when replication is broken. I encountered this while investigating an incident in which both replicas stopped receiving transactions, the primary remained online, and application writes slowed down.
In Part 3, we covered how MOCO's semi-synchronous replication can make missing replica acknowledgements affect write availability. Here we'll focus on troubleshooting and recovery .
The examples use a MOCO cluster, eks-db , in the database namespace:
MySQL instance Kubernetes pod Role in this example
eks-db-0 moco-eks-db-0 Replica
eks-db-1 moco-eks-db-1 Primary
eks-db-2 moco-eks-db-2 Replica
The current primary must always be checked first. MOCO can change the primary during failover or switchover, so these roles are examples, not fixed assignments.
1.β¦