#查看如下两个参数为YES，说明从库运行正常。
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
# 主库插入一条记录
mysql> use mydb;
Database changed
mysql> select * from stu;
+----+----------+----------+
| id | username | password |
+----+----------+----------+
| 1 | koumm | 123456 |
| 2 | zhangsan | 123456 |
| 3 | lisi | 123456 |
| 4 | wangwu | 123456 |
| 5 | zhaoliu | 123456 |
| 6 | zhouqi | 123456 |
+----+----------+----------+
6 rows in set (0.00 sec)
mysql>
mysql> INSERT INTO stu VALUES ('7', 'tom', '123456');
Query OK, 1 row affected (0.05 sec)
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
mysql>
# 从库查询同步情况mysql> use mydb;
Database changed
mysql> select * from stu;
+----+----------+----------+
| id | username | password |
+----+----------+----------+
| 1 | koumm | 123456 |
| 2 | zhangsan | 123456 |
| 3 | lisi | 123456 |
| 4 | wangwu | 123456 |
| 5 | zhaoliu | 123456 |
| 6 | zhouqi | 123456 |
| 7 | tom | 123456 |
+----+----------+----------+
7 rows in set (0.00 sec)
mysql>
小结：本文只是配置mysql主从的一个过程。还是有很多需要考虑与改进的地址。
(1) 主从库同步用户权限的问题考虑，是直接从主库同步权限呢，还是单独考虑从库的权限。
(2) mysql5.5有半自动主从同步复制
(3) mysql5.6有基于GTID主从复制
二、快速配置从库方式二
1，主库备份(全库备份)
mysqldump -uroot -p -A -B --events --master-data=1 > mydb.sql
全库备份记录了数据库备份时的master-bin.000003', MASTER_LOG_POS=583位置，在配置从库时无需要在主库锁表，记录POS位置，解锁等配置。
[root@localhost ~]# egrep -v "#|\*|--|^$" mydb.sql |head
CHANGE MASTER TO MASTER_LOG_FILE='master-bin.000003', MASTER_LOG_POS=583;
USE `mydb`;
DROP TABLE IF EXISTS `user`;
CREATE TABLE `user` (
`id` varchar(20) NOT NULL,
`username` varchar(20) NOT NULL,
`password` char(32) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
LOCK TABLES `user` WRITE;
2，从库创建同步的数据库, 并导入数据
mysql -uroot -padmin
create database mydb;
mysql -uroot -padmin mydb < mydb.sql
3，配置主从同步
mysql>
CHANGE MASTER TO
MASTER_HOST='192.168.0.65',
MASTER_PORT=3306,
MASTER_USER='repl',
MASTER_PASSWORD='123456';
mysql> start slave;
Query OK, 0 rows affected (0.02 sec)
mysql> show slave status \G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.0.65
Master_User: repl
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: master-bin.000003
Read_Master_Log_Pos: 583
Relay_Log_File: testdb-relay-bin.000004
Relay_Log_Pos: 747
Relay_Master_Log_File: master-bin.000003
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: mysql.%
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 583
Relay_Log_Space: 2536
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: c8bb22a1-024e-11e6-a1e8-000c29225fa0
Master_Info_File: /usr/local/mysql-5.6.29-linux-glibc2.5-x86_64/data/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
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
1 row in set (0.00 sec)
三、主从同步简单管理
1. 停止MYSQL同步