操作过程
- 主服务(Master)配置服务id、开启二进制日志功能(bin-log)
- 主服务创建用户(用来同步数据)
- 从服务(Slave)配置服务id
- 从服务配置master的用户信息、日志信息，开启同步(start slave)
安装docker
拉取mysql镜像
$ docker pull mysql:5.7
创建主从服务容器
mysql主服务 端口3307，密码root
$ docker run -p 3307:3306 --name mysql_master -e MYSQL_ROOT_PASSWORD=root -d mysql:5.7
mysql从服务 端口3308，密码root
$ docker run -p 3308:3306 --name mysql_slave -e MYSQL_ROOT_PASSWORD=root -d mysql:5.7
配置主服务
进入主服务容器
$ docker exec -it a00792eaeeb4 /bin/bash
找到配置文件目录
$ cd /etc/mysql/mysql.conf.d
安装vim
修改配置
$ vim mysqld.cnf
[mysqld]
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
datadir = /var/lib/mysql
#log-error = /var/log/mysql/error.log
# By default we only accept connections from localhost
#bind-address = 127.0.0.1
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
#新添加的配置
server-id = 1
log-bin = mysql-bin
binlog-format = mixed
保存后重启mysql服务、重启容器
$ service mysql restart
$ docker restart a00792eaeeb4
创建一个同步复制的用户slave，密码为123456，授予用户slave REPLICATION SLAVE权限和REPLICATION CLIENT权限，该用户用于在主从库之间同步数据。
mysql> CREATE USER 'slave'@'%' IDENTIFIED BY '123456';
mysql> GRANT REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'slave'@'%';
查看配置状态
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 | 435 | | | |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
记下这里的位置：435，在下面数据同步时要用到
配置从服务
同样进入容器，编辑/etc/mysql/mysql.conf.d/mysqld.cnf
[mysqld]
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
datadir = /var/lib/mysql
#log-error = /var/log/mysql/error.log
# By default we only accept connections from localhost
#bind-address = 127.0.0.1
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
#新加的内容
server-id = 2
保存后重启容器
$ docker restart 2061a7aaa728
先查询Master服务的ip地址
$ docker inspect --format='{{.NetworkSettings.IPAddress}}' a00792eaeeb4
172.17.0.2
然后进入Slave服务，开始配置数据同步
$ docker exec -it 2061a7aaa728 /bin/bash
$ mysql -uroot -proot
先停止从服务的slave，
mysql> stop slave;
Query OK, 0 rows affected, 1 warning (0.00 sec)
拿到从上面Master的位置435，执行：
mysql> change master to master_host='172.17.0.2', master_user='slave', master_password='123456', master_port=3306, master_log_file='mysql-bin.000001', master_log_pos= 435;
然后再启动slave，开启同步
mysql> start slave;
解释
CHANGE MASTER TO
MASTER_HOST='172.17.0.2',//主服务的IP地址
master_port=3306,//主服务的服务端口
MASTER_USER='slave',//主服务用户
MASTER_PASSWORD='123456',//主服务用户密码
MASTER_LOG_FILE='mysql-bin.000001',//日志文件
MASTER_LOG_POS=435;//日志位置
这个时候，查看SLave服务的slave状态：
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 172.17.0.2
Master_User: slave
Master_Port: 3306
Connect_Retry: 30
Master_Log_File: mysql-bin.000001
Read_Master_Log_Pos: 435
Relay_Log_File: dbc647dfde50-relay-bin.000002
Relay_Log_Pos: 515
Relay_Master_Log_File: mysql-bin.000001
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 435
Relay_Log_Space: 729
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
Master_UUID: 1af39b3e-13d2-11e9-ae89-0242ac110002
Master_Info_File: /var/lib/mysql/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)
如果显示 Slave_IO_Running: Yes,Slave_SQL_Running: Yes，那么说明配置成功。
如果失败，可能原因是：
- ip地址不对，如果用docker的话，Master的host不是localhost或127.0.0.0，而需要通过
docker inspect --format='{{.NetworkSettings.IPAddress}}' 容器id来查询ip地址 - 端口不对，这里端口是mysql服务的端口3306，而不是docker对外访问的端口3307
- 密码错误，这里的用户名密码是Master服务上新创建的，专门做数据同步的用户，而不是Slave的用户
- 日志文件名或位置不对，这里需要在Master服务执行
show master status;来获取日志名和位置
测试主从同步
在Master服务新建数据库test
CREATE DATABASE `test` DEFAULT CHARACTER SET = `utf8mb4`;
然后查看Slave服务
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| sys |
| test |
+--------------------+
5 rows in set (0.00 sec)
在Master服务建个表user
CREATE TABLE `user` (
`id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(20) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
查看从服务Slave：
mysql> use test;
Database changed
mysql> show tables;
+----------------+
| Tables_in_test |
+----------------+
| user |
+----------------+
1 row in set (0.00 sec)
在Master新加数据，查看Slave
注意
如果在Master服务增删改数据，都会同步到Slave。但是如果在Slave修改数据后，无法同步到Master，并且日志文件会错乱（Slave除非重新设置日志文件位置），导致数据无法完成同步。所以一般Master服务给读写权限，而Slave只需要读权限，禁止写入数据。
3078
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
