MySQL Master Slave Docker部署例子

原文地址:https://chanjarster.github.io...html

本文对应代码:githubmysql

用Docker部署基于GTID的MySQL Master-Slave Replication例子。git

启动Master

写一个文件mysql-master.cnfgithub

[mysqld]
server_id=1
binlog_format=ROW
gtid_mode=ON
enforce-gtid-consistency=true

这个配置文件把Master的server_id设置为1,要注意在同一个Master-Slave集群里,server_id不能重复。sql

启动Master:docker

docker run -d --name mysql-master \
  -e MYSQL_USER=my_user \
  -e MYSQL_DATABASE=my_database \
  -e MYSQL_PASSWORD=my_database_password \
  -e MYSQL_ROOT_PASSWORD=my_root_password \
  -p 3307:3306 \
  -v $(pwd)/mysql-master.cnf:/etc/mysql/conf.d/mysql-master.cnf \
  mysql:8.0 \
  --log-bin=my

启动Slave

写一个文件mysql-slave-1.cnfbash

[mysqld]
server_id=2
binlog_format=ROW
gtid_mode=ON
enforce-gtid-consistency=true
read_only=ON

这个文件把Slave的server_id设置为2,若是你有多个Slave,那么得分别设置不一样的server_id。此外,将Slave设置为read_only模式(这样就不能在slave上执行写操做了)。ide

启动Slave:post

docker run -d --name mysql-slave-1 \
  -e MYSQL_ROOT_PASSWORD=my_root_password \
  -p 3308:3306 \
  -v $(pwd)/mysql-slave-1.cnf:/etc/mysql/conf.d/mysql-slave-1.cnf \
  mysql:8.0 \
  --skip-log-bin \
  --skip-log-slave-updates \
  --skip-slave-start

建立Replication用户

到Master上建立Replication用户:code

$ docker exec -it mysql-master mysql -u root -p
Enter password: my_root_password

mysql> CREATE USER 'repl'@'%' IDENTIFIED BY 'password';
mysql> GRANT REPLICATION SLAVE ON *.* TO 'repl'@'%';

将Slave和Master关联

到Slave上把本身和Master关联起来:

$ docker exec -it mysql-slave-1 mysql -u root -p
Enter password: my_root_password

mysql> CHANGE MASTER TO 
  MASTER_HOST='192.168.101.21',
  MASTER_PORT=3307,
  MASTER_USER='repl',
  MASTER_PASSWORD='password',
  GET_MASTER_PUBLIC_KEY=1,
  MASTER_AUTO_POSITION=1;

注意MASTER_HOST写的是Master所在的Host的IP,MASTER_PORT写的是Master暴露在Host上的端口,MASTER_USERMASTER_PASSWORD则是Replication用户的信息。

最后正式启动Slave:

mysql> START SLAVE;

验证

到Slave上看看my_database是否存在:

$ docker exec -it mysql-slave-1 mysql -u root -p
Enter password: my_root_password

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| my_database        |
| mysql              |
| performance_schema |
| sys                |
+--------------------+
5 rows in set (0.01 sec)

若是有就说明my_database从Master复制到了Slave上。

docker-compose版本

github上也提供了docker-compose.yaml,操做过程和上述一致,只不过容器名字会有变化。

# 拉起Master和Slave
$ docker-compose -p mysql-repl up
# 链接Master
$ docker exec -it mysql-repl_mysql-master_1 mysql -u root -p
# 链接Slave
$ docker exec -it mysql-repl_mysql-slave_1 mysql -u root -p

而且CHANGE MASTER TO语句有所不一样,使用的是Master的Service Name以及容器内端口3306

CHANGE MASTER TO 
  MASTER_HOST='mysql-master',
  MASTER_PORT=3306,
  MASTER_USER='repl',
  MASTER_PASSWORD='password',
  GET_MASTER_PUBLIC_KEY=1,
  MASTER_AUTO_POSITION=1;

Troubleshooting

docker run版本在Mac上没法工做

这个是由于Slave容器没法访问到Master的host。解决办法我也不知道。

关于GET_MASTER_PUBLIC_KEY

在作本例子时出现过Slave没法链接到Master的状况:

2019-06-19T01:34:24.361566Z 8 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='mysql-master', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2019-06-19T01:34:28.274728Z 9 [Warning] [MY-010897] [Repl] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2019-06-19T01:34:28.330825Z 9 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error connecting to master 'repl@mysql-master:3306' - retry-time: 60  retries: 1, Error_code: MY-002061
2019-06-19T01:35:28.333735Z 9 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error connecting to master 'repl@mysql-master:3306' - retry-time: 60  retries: 2, Error_code: MY-002061
2019-06-19T01:36:28.335525Z 9 [ERROR] [MY-010584] [Repl] Slave I/O for channel '': error connecting to master 'repl@mysql-master:3306' - retry-time: 60  retries: 3, Error_code: MY-002061
...

详细细节可见这个issue,这是由于MySQL 8默认启用了caching_sha2_password authentication plugin,issue中提到了一个办法:在启动Slave的时候添加--default-auth=mysql_native_password参数。不过我感受这个不太好,查阅相关文档后发现能够在CHANGE MASTER TO添加GET_MASTER_PUBLIC_KEY=1参数来解决这个问题。

更多详情参考caching_sha2_password and ReplicationCHANGE MASTER TO Syntax

参考资料

相关文章
相关标签/搜索