Introducing MOCO, a modern MySQL operator on Kubernetes
We are proud to announce a new MySQL operator named MOCO. MOCO manages MySQL clusters on Kubernetes that replicate data using GTID-based semi-synchronous replication.
Presslabs' operator is being developed, but the last release was almost a year ago. It does not yet support MySQL 8 and is noted as follows:
With properly configured semi-synchronous replication, completed transactions will not be lost after a failure in the source instance. However, the source instance may result in having errant transactions after recovering from the failure.
Errant transactions are transactions that do not exist in the new source instance, so the old source instance having errant transactions should not re-join the cluster.
Group replication prevents errant transactions by adopting Paxos-based consensus protocol. But it has a number of limitations.
We did not investigate Galera Cluster and XtraDB Cluster in detail because we found out early that they could not meet our requirements.
/cdn.vox-cdn.com/uploads/chorus_asset/file/25745083/copilotplusprompt.jpeg)
