Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Docker Automatic MySQL Slave Propagation

DZone's Guide to

Docker Automatic MySQL Slave Propagation

This article covers the steps needed to set up automated MySQL slave nodes using Docker.

· Database Zone
Free Resource

Find out how Database DevOps helps your team deliver value quicker while keeping your data safe and your organization compliant. Align DevOps for your applications with DevOps for your SQL Server databases to discover the advantages of true Database DevOps, brought to you in partnership with Redgate

In this post, we'll discuss Docker automatic MySQL slave propagation for help with scaling.

In my previous posts on the Docker environment, I covered Percona XtraDB Cluster. Percona XtraDB Cluster can automatically scale by conveniently adding new nodes using the highly automated State Snapshot Transfer. State Snapshot Transfer allows a new node to copy data from an existing node (I still want to see how this is possible with MySQL Group Replication).

This is not the case with regular MySQL Replication. With MySQL Replication, the slave setup still requires manual steps (well, unless you've already scripted it for your environment). At least these are "simple" steps (ha!). Percona XtraBackup can setup replication with less work (see this link for details), but it still requires poking around and switching between servers.

However, nothing stops us from making it more automatic (similar to SST in Percona XtraDB Cluster), especially with Docker images. Why Docker? Because Docker provides a highly controlled environment where we can orchestrate how scripts get executed. Severalnines provides a great intro into MySQL with Docker.

There are a few more components for this setup:

Before jumping to my solution, I should point to some work in this area by Joyent.

I propose my image with sources on GitHub.

First, we need to start a master node:

docker run-d-p3306:3306--net=replicaset_net

--name=replicaset_master

-eMYSQL_ROOT_PASSWORD=Theistareyk

perconalab/ps-master-slave--innodb-buffer-pool-size=2G

I assume that we've created the network replicaset_net already, either bridge or overlay.

You can create a slave by pointing to the master container:

docker run-d-p3306--net=replicaset_net

--name=replicaset_slave1

-eMYSQL_ROOT_PASSWORD=Theistareyk

-eMASTER_HOST=replicaset_master

perconalab/ps-master-slave--innodb-buffer-pool-size=2G

The started node will automatically connect to MASTER_HOST, copy the data and perform all the steps needed to start the slave.

You can even copy data from a running slave, instead of the master, like this:

docker run-d-p3306--net=replicaset_net

--name=replicaset_slave2

-eMYSQL_ROOT_PASSWORD=Theistareyk

-eMASTER_HOST=replicaset_master

-eSLAVE_HOST=replicaset_slave1

perconalab/ps-master-slave--innodb-buffer-pool-size=2G


Docker Network lets you use container names "replicaset_master" and "replicaset_slave1" instead of IP addresses, which is very convenient.

As the result of above, we have one master and two slaves running. We can start as many slave nodes as needed.

Please remember, this is more proof-of-concept than "production ready" images, but it gives a good direction for implementation.

Align DevOps for your applications with DevOps for your SQL Server databases to increase speed of delivery and keep data safe. Discover true Database DevOps, brought to you in partnership with Redgate

Topics:
docker images ,cluster ,xtradb ,slave ,snapshot ,docker ,state ,mysql ,performance ,percona

Published at DZone with permission of Vadim Tkachenko, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}