老司机带你还原主从复制细节

主从复制，建立一个和主数据库完全一样的数据库环境，称为从数据库，主数据库一般是准实时的业务数据库。
1、主负责写，从负责读 用于读写分离
2、通过binlog 二进制日志和日志偏移量实现
主服务器 /etc/ny.cnf

[client]
port = 3306
socket = /tmp/mysql.sock
[mysqld]
replicate-ignore-db = mysql
replicate-ignore-db = test
replicate-ignore-db = information_schema
user = mysql
port = 3306
#基于事务的主从复制
enforce_gtid_consistency = ON
log_slave_updates = ON
gtid_mode = ON
#################
socket = /tmp/mysql.sock
basedir = /usr/local/webserver/mysql
datadir = /www/data_mysql
log-error = /usr/local/webserver/mysql/mysql_error.log
pid-file = /usr/local/webserver/mysql/mysql.pid
open_files_limit = 65535
back_log = 600
max_connections = 5000
max_connect_errors = 1000
table_open_cache = 1024
external-locking = FALSE
max_allowed_packet = 32M
sort_buffer_size = 1M
join_buffer_size = 1M
thread_cache_size = 600
#thread_concurrency = 8
query_cache_size = 128M
query_cache_limit = 2M
query_cache_min_res_unit = 2k
default-storage-engine = MyISAM
default-tmp-storage-engine=MYISAM
thread_stack = 192K
transaction_isolation = READ-COMMITTED
tmp_table_size = 128M
max_heap_table_size = 128M
log-slave-updates
log-bin = /usr/local/webserver/mysql/binlog/binlog
#binlog-do-db=test
#binlog-ignore-db=mysql
binlog_cache_size = 4M
binlog_format = MIXED
max_binlog_cache_size = 8M
max_binlog_size = 1G
relay-log-index = /usr/local/webserver/mysql/relaylog/relaylog
relay-log-info-file = /usr/local/webserver/mysql/relaylog/relaylog
relay-log = /usr/local/webserver/mysql/relaylog/relaylog
expire_logs_days = 10
key_buffer_size = 256M
read_buffer_size = 1M
read_rnd_buffer_size = 16M
bulk_insert_buffer_size = 64M
myisam_sort_buffer_size = 128M
myisam_max_sort_file_size = 10G
myisam_repair_threads = 1
myisam_recover
interactive_timeout = 120
wait_timeout = 120
skip-name-resolve
#master-connect-retry = 10
slave-skip-errors = 1032,1062,126,1114,1146,1048,1396
#master-host = 192.168.1.2
#master-user = username
#master-password = password
#master-port = 3306
server-id = 1
loose-innodb-trx=0 
loose-innodb-locks=0 
loose-innodb-lock-waits=0 
loose-innodb-cmp=0 
loose-innodb-cmp-per-index=0
loose-innodb-cmp-per-index-reset=0
loose-innodb-cmp-reset=0 
loose-innodb-cmpmem=0 
loose-innodb-cmpmem-reset=0 
loose-innodb-buffer-page=0 
loose-innodb-buffer-page-lru=0 
loose-innodb-buffer-pool-stats=0 
loose-innodb-metrics=0 
loose-innodb-ft-default-stopword=0 
loose-innodb-ft-inserted=0 
loose-innodb-ft-deleted=0 
loose-innodb-ft-being-deleted=0 
loose-innodb-ft-config=0 
loose-innodb-ft-index-cache=0 
loose-innodb-ft-index-table=0 
loose-innodb-sys-tables=0 
loose-innodb-sys-tablestats=0 
loose-innodb-sys-indexes=0 
loose-innodb-sys-columns=0 
loose-innodb-sys-fields=0 
loose-innodb-sys-foreign=0 
loose-innodb-sys-foreign-cols=0

slow_query_log_file=/usr/local/webserver/mysql/mysql_slow.log
long_query_time = 1
[mysqldump]
quick
max_allowed_packet = 32M

从服务器 /etc/my.cnf

[client]
port = 3306
socket = /tmp/mysql.sock

[mysqld]
server-id=2
#replicate-do-db=test
#replicate-ignore-db=mysql
##########
enforce_gtid_consistency = ON
log_slave_updates = ON
gtid_mode = ON
###################
relay-log-index=slave-relay-bin.index
relay-log=slave-relay-bin
character_set_server=utf8
init_connect='SET NAMES utf8'
basedir=/usr/local/mysql
datadir=/usr/local/mysql/data
socket=/tmp/mysql.sock
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
#²»ȸ·ִ𐢐´
lower_case_table_names = 1

sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

max_connections=5000

default-time_zone = '+8:00'

实现细节

一、配置主从复制
我的服务器信息：
主服务器master:10.128.136.144
从服务器save1: 10.128.136.145
常规的基于二进制日志+偏移量、加强的基于gtid 一个uuid、基于GTID的复制可以忽略已经执行过的事务，减少了数据发生不一致的风险
1.主从复制
（1） 在主数据库上创建用于主从复制的账户（需要在主从服务器上都创建复制账户）
[mysql @master ~]# mysql –u root –p
mysql> GRANT REPLICATION SLAVE ON *.* TO 'repl'@'%' IDENTIFIED BY 'repl';
Query OK, 0 rows affected (0.00 sec)
注意：以上命令中的IP地址，是数据库服务器所在网段的IP地址。Repl是账户名，密码是repl  注意：主库、从库都需要执行这个命令
（2）主数据库锁表(禁止再插入数据以获取主数据库的的二进制日志坐标)(由于都是重新安装数据库，因此此步骤可以跳过)
在主数据库上操作
mysql> flush tables with read lock;

Query OK, 0 rows affected (0.00 sec)

（3）查看主数据库的状态(并记录下File字段和Position字段的值，在配置从服务器时有用到)
在主数据库上操作
mysql> show master status;
+------------------------+----------+--------------+------------------+-------------------+
| File                  | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------------+----------+--------------+------------------+-------------------+
| mysqlmaster-bin.000001 |      310 |              |                  |                  |
+------------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

（4）创建主数据库的快照文件(此步骤可以跳过)

[mysql @master ~]# cd /usr/bin/

[mysql @master ~]# ./mysqldump -uroot -p –h10.128.136.144 -P3306 --all-databases --triggers --routines --events >>/mnt/ all.sql

将生成的all.sql放在其它任何目录下，然后使用scp命令复制到远程从数据库服务器的某个目录中。这条命令的执行时间根据数据量的不同，会有所不同，如果主数据库的数据量很大，可能需要很长时间，那么在这种情况下，就最好在晚上没有业务的时候进行这个操作。
（5） 解锁主数据库的锁表操作(此步骤可以跳过)
[mysql @master ~]# mysql -uroot -p   
mysql> unlock tables;
Query OK, 0 rows affected (0.00 sec)

（6） 在从数据库服务器上导入第3.4步创建的快照文件到从数据库中(此步骤可以跳过)
[mysql @slave1 ~]# mysql -uroot -p -h10.128.136.145 -P3306 < /mnt/ all.sql
（7） 在从数据库服务器上设置主数据库服务器向从数据库服务器同步
[mysql @slave1 ~]# mysql -uroot -p
mysql> change master to master_host = '10.128.136.144',master_user='repl',master_password=’mysql’,master_log_file='mysqlmaster-bin.000001',master_log_pos=310;
注意：红色部分的值，是在第3.3步中查出来的。
（8）启动从数据库复制线程
mysql> start slave;
Query OK, 0 rows affected (0.01 sec)

（9）查询从数据库的复制线程状态
mysql> show slave status \G
*************************** 1. row ***************************
              Slave_IO_State: Waiting for master to send event
                  Master_Host: 10.128.136.144
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysqlmaster-bin.000004
          Read_Master_Log_Pos: 327
              Relay_Log_File: slave-relay-bin.000002
                Relay_Log_Pos: 289
        Relay_Master_Log_File: mysqlmaster-bin.000004
          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: 327
              Relay_Log_Space: 462
              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: 2e5e1b22-f0a9-11e3-bbac-000c297799e0
            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 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)
如果Slave_IO_Running和Slave_SQL_Running两项都为yes，就表示主从复制配置成功了.一个为否的话，需要重新 change to master ....指定二进制文件和位置、 Last_SQL_Error 关注这些错误
2.基于gtid主从复制
https://segmentfault.com/a/1190000014322393
从 MySQL 5.6.5 开始新增了一种基于 GTID 的复制方式。通过 GTID保证了每个在主库上提交的事务在集群中有一个唯一的ID。这种方式强化了数据库的主备一致性，故障恢复以及容错能力。
在原来基于二进制日志的复制中，从库需要告知主库要从哪个偏移量进行增量同步，如果指定错误会造成数据的遗漏，从而造成数据的不一致。借助GTID，在发生主备切换的情况下，MySQL的其它从库可以自动在新主库上找到正确的复制位置，这大大简化了复杂复制拓扑下集群的维护，也减少了人为设置复制位置发生误操作的风险。另外，基于GTID的复制可以忽略已经执行过的事务，减少了数据发生不一致的风险。

主库和从库my.cnf文件中添加参数：
enforce_gtid_consistency = ON
log_slave_updates = ON
gtid_mode = ON
（1） 在主数据库上创建用于主从复制的账户（需要在主从服务器上都创建复制账户）
[mysql @master ~]# mysql –u root –p
mysql> GRANT REPLICATION SLAVE ON *.* TO 'repl'@'%' IDENTIFIED BY 'repl';
Query OK, 0 rows affected (0.00 sec)
注意：以上命令中的IP地址，是数据库服务器所在网段的IP地址。Repl是账户名，密码是repl
（2）默认主从数据一致： 基于事务的多加一句配置即可
mysql>change master to master_host='10.128.136.144,master_port=3306,master_user='repl',master_password='repl',master_auto_position=1;
（3）启动从数据库复制线程
mysql> start slave;
Query OK, 0 rows affected (0.01 sec)
（4）查询从数据库的复制线程状态
mysql> show slave status \G
*************************** 1. row ***************************
              Slave_IO_State: Waiting for master to send event
                  Master_Host: 10.128.136.144
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysqlmaster-bin.000001
          Read_Master_Log_Pos: 327
              Relay_Log_File: slave-relay-bin.000001
                Relay_Log_Pos: 289
        Relay_Master_Log_File: mysqlmaster-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: 327
              Relay_Log_Space: 462
              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: 2e5e1b22-f0a9-11e3-bbac-000c297799e0
            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 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: a9fd4765-ec70-11e6-b543-0242ac140002:1-4
           Executed_Gtid_Set: a9fd4765-ec70-11e6-b543-0242ac140002:1-4
                Auto_Position: 1
1 row in set (0.00 sec)

Slave_IO_Running和Slave_SQL_Running两项都为yes，就表示主从复制配置成功了.

你发现了吗，上面的主从复制有什么缺点？ 一个主多个从、从1挂了无所谓，可以正常提供服务–一旦主挂了，岂不是jj了、因此这种简单的主从复制不可用于生产的高可用环境
1、生产的高可用需要如下架构–需要另一个热备主、主挂掉，vip可以自动切换热备主