![]() ![]() Relay_Log_File: cluster1-pxc-0-relay-bin-ps_to_pxc1. Slave_IO_State: Waiting for master to send event ![]() Kubectl exec -it cluster1-pxc-0 -c pxc - mysql -uroot -proot_password -e "show replica status \G" Deploy Percona Distribution for MySQL Operator on Kubernetes (I have used GKE 1.20). Migration Configure the target PXC cluster managed by k8s operator:ġ. Configure asynchronous replication between MySQL server and PXC cluster managed by k8s operator.Īs a result, we have asynchronous replication between MySQL server and PXC cluster in k8s which is in read-only mode. Perform the restore of the MySQL database from the S3 bucket into the PXC cluster which is deployed in k8s.ģ. Make the MySQL database backup using Percona XtraBackup and upload it to the S3 bucket using xbcloud.Ģ. The following steps should be done to perform the migration procedure:ġ. AWS S3 bucket is used to save the backup from MySQL DB and then to restore the PXC cluster in k8s. Google Kubernetes Engine (GKE) cluster where Percona Distribution for MySQL Operator is deployed with PXC cluster (as a target).ģ. Depending on your topology of DB deployment, you can use several servers to use synchronous connection failover mechanism on the operator’s end.Ģ. In my test deployment, I use only one server as a Source to simplify the deployment. Millions of queries per second Hundreds of. MySQL 8.0.23 database (in my case it is Percona Server for MySQL ) which is deployed in DO (as a Source) and Percona XtraBackup for the backup. Built at Google to scale, Vitess is proven as the most scalable open source database out there. ![]() This approach helps you reduce downtime and data loss for your application.ġ. Connect Datadog
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |