mysql5.6 replication_MySQL5.6 Replication主从复制（读写分离) 配置完整版
MySQL5.6主從復(fù)制(讀寫(xiě)分離)教程
1、MySQL5.6開(kāi)始主從復(fù)制有兩種方式：
基于日志(binlog)；
基于GTID(全局事務(wù)標(biāo)示符)。
需要注意的是：GTID方式不支持臨時(shí)表！所以如果你的業(yè)務(wù)系統(tǒng)要用到臨時(shí)表的話(huà)就不要考慮這種方式了，
至少目前最新版本MySQL5.6.12的GTID復(fù)制還是不支持臨時(shí)表的。
所以本教程主要是告訴大家如何通過(guò)日志(binlog)方式做主從復(fù)制！
2、MySQL官方提供的MySQL Replication教程：
http://dev.mysql.com/doc/refman/5.6/en/replication.html
第一步：準(zhǔn)備工作
主服務(wù)器: 192.168.1.100
從服務(wù)器: 192.168.1.101
MySQL軟件版本：
MySQL-server-advanced-5.6.18-1.el6.x86_64.rpm
MySQL-cient-advanced-5.6.18-1.el6.x86_64.rpm
第二步：在主服務(wù)器和從服務(wù)器上安裝MySQL數(shù)據(jù)庫(kù)軟件
安裝方法，請(qǐng)參見(jiàn)
MySQL5.6.18 for RHEL/OralceLinux 6.5 安裝
MySQL數(shù)據(jù)庫(kù)軟件安裝完成后，不要急著做mysql啟動(dòng)操作。建議把mysql初始化生成的/usr/my.cnf
(如果是從源文件編譯安裝時(shí)，路徑應(yīng)該是在/usr/local/mysql/mysql.cnf)刪除，然后把優(yōu)化好的mysql
配置文件my.cnf放到/etc下。
第三步：修改主數(shù)據(jù)庫(kù)的配置文件/usr/my.cnf
[mysqld]
server-id=1
log-bin=mysqlmaster-bin.log
sync_binlog=1
innodb_buffer_pool_size=512M
innodb_flush_log_at_trx_commit=1
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
lower_case_table_names=1
log_bin_trust_function_creators=1
第四步：修改從數(shù)據(jù)庫(kù)配置文件/usr/my.cnf
server-id=2
log-bin=mysqlslave-bin.log
sync_binlog=1
innodb_buffer_pool_size=512M
innodb_flush_log_at_trx_commit=1
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
lower_case_table_names=1
log_bin_trust_function_creators=1
第五步：在主數(shù)據(jù)庫(kù)和從數(shù)據(jù)庫(kù)服務(wù)器上分別執(zhí)行以下命令重新啟動(dòng)主數(shù)據(jù)庫(kù)和從數(shù)據(jù)庫(kù)
[root@master ~]# service mysql restart
[root@slave ~]# service mysql restart
第六步：在主數(shù)據(jù)庫(kù)上創(chuàng)建用于主從復(fù)制的賬戶(hù)
[root@master ~]# mysql -uroot -p
mysql> GRANT REPLICATION SLAVE ON *.* TO 'repl'@'192.168.1.101' IDENTIFIED BY '111111';
Query OK, 0 rows affected (0.00 sec)
注意：以上命令中的IP地址，是從數(shù)據(jù)庫(kù)服務(wù)器的IP地址。
第七步：主數(shù)據(jù)庫(kù)鎖表(禁止再插入數(shù)據(jù)以獲取主數(shù)據(jù)庫(kù)的的二進(jìn)制日志坐標(biāo))
mysql> flush tables with read lock;
Query OK, 0 rows affected (0.00 sec)
第八步：查看主數(shù)據(jù)庫(kù)的狀態(tài)(并記錄下File字段和Position字段的值，在配置從服務(wù)器時(shí)有用到)
mysql> show master status;
+------------------------+----------+--------------+------------------+-------------------+
| File ? ? ? ? ? ? ? ? ? | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------------+----------+--------------+------------------+-------------------+
| mysqlmaster-bin.000004 | ? ? ?327 | ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? |
+------------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
第九步：創(chuàng)建主數(shù)據(jù)庫(kù)的快照文件
[root@master ~]# cd /usr/bin/
# ./mysqldump -uroot -p -h127.0.0.1 -P3306 --all-databases --triggers --routines --events >>/mnt/windows/all.sql
上面命令中的紅色部分，是一個(gè)共享目錄，這個(gè)目錄可以同時(shí)被主數(shù)據(jù)庫(kù)服務(wù)器和從數(shù)據(jù)庫(kù)服務(wù)器訪(fǎng)問(wèn)到。
如果沒(méi)有這樣的共享目錄，可以將all.sql放在其它任何目錄下，然后使用scp命令復(fù)制到遠(yuǎn)程從數(shù)據(jù)庫(kù)服務(wù)器的某個(gè)目錄中
這條命令的執(zhí)行時(shí)間根據(jù)數(shù)據(jù)量的不同，會(huì)有所不同，如果主數(shù)據(jù)庫(kù)的數(shù)據(jù)量很大，可能需要很長(zhǎng)時(shí)間，那么在這種情況下，就最好在
晚上沒(méi)有業(yè)務(wù)的時(shí)候進(jìn)行這個(gè)操作，否則第七步中的鎖表操作會(huì)對(duì)業(yè)務(wù)系統(tǒng)造成很大的影響
第十步：解鎖主數(shù)據(jù)庫(kù)的鎖表操作
[root@master ~]# mysql -uroot -p ? ?(本命令在主數(shù)據(jù)庫(kù)服務(wù)器上執(zhí)行)
mysql> unlock tables;
Query OK, 0 rows affected (0.00 sec)
第十一步：在從數(shù)據(jù)庫(kù)服務(wù)器上導(dǎo)入第七步創(chuàng)建的快照文件到從數(shù)據(jù)庫(kù)中
[root@slave ~]# mysql -uroot -p -h127.0.0.1 -P3306 < /mnt/windows/all.sql
第十二步：在從數(shù)據(jù)庫(kù)服務(wù)器上設(shè)置主數(shù)據(jù)庫(kù)服務(wù)器向從數(shù)據(jù)庫(kù)服務(wù)器同步
[root@slave ~]# mysql -uroot -p
mysql> change master to master_host = '192.168.1.100',master_user='repl',master_password='111111',master_log_file='mysqlmaster-bin.000004',master_log_pos=327;
注意：紅色部分的值，是在第八步中查出來(lái)的，這里不能弄錯(cuò)了
第十三步：啟動(dòng)從數(shù)據(jù)庫(kù)復(fù)制線(xiàn)程
mysql> start slave;
Query OK, 0 rows affected (0.01 sec)
第十四步：查詢(xún)從數(shù)據(jù)庫(kù)的復(fù)制線(xiàn)程狀態(tài)
mysql> show slave status \G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.1.100
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兩項(xiàng)都為yes，就表示主從復(fù)制配置成功了.
下面可以開(kāi)始測(cè)試配置是否成功了，首先在主數(shù)據(jù)庫(kù)的test數(shù)據(jù)庫(kù)中新建一張表，然后插入幾條數(shù)據(jù)，然后到從數(shù)據(jù)庫(kù)看看是否同步過(guò)來(lái)了。
注意：當(dāng)從數(shù)據(jù)庫(kù)有大量的查詢(xún)時(shí)，可以暫時(shí)將從數(shù)據(jù)庫(kù)的復(fù)制線(xiàn)程關(guān)閉掉，等查詢(xún)量降下來(lái)了，再打開(kāi)，這樣也不會(huì)丟失數(shù)據(jù)。
附：一個(gè)優(yōu)化好后的主數(shù)據(jù)庫(kù)配置文件和從數(shù)據(jù)配置文件內(nèi)容如下：
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
[client]
port=3306
socket=/usr/local/mysql/mysql.sock
default-character-set=utf8
[mysqld]
sync_binlog=1
server-id=1
port=3306
socket=/usr/local/mysql/mysql.sock
pid-file=/home/mysql/temp/my3306.pid
user=mysql
datadir=/home/mysql/data
tmpdir=/home/mysql/temp/
log-bin=/home/mysql/data/mysqlmaster-bin
log-error=/home/mysql/logs/error.log
slow_query_log_file=/home/mysql/logs/slow.log
binlog_format=mixed
slow_query_log
long_query_time=10
wait_timeout=31536000
interactive_timeout=31536000
max_connections=500
max_user_connections=490
max_connect_errors=2
character_set_server=utf8
skip-external-locking
key_buffer_size = 128M
max_allowed_packet = 5M
table_open_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 4
binlog-ignore-db=mysql
binlog-ignore-db=information_schema
replicate_ignore_db=mysql
replicate_ignore_db=information_schema
expire-logs-days=10
skip-slave-start
skip-name-resolve
lower_case_table_names=1
log_bin_trust_function_creators=1
# InnoDB
innodb_data_home_dir=/home/mysql/data
innodb_log_group_home_dir=/home/mysql/logs
innodb_data_file_path=ibdata1:128M:autoextend
innodb_buffer_pool_size=2G
innodb_log_file_size=10M
innodb_log_buffer_size=8M
innodb_lock_wait_timeout=50
innodb_file_per_table
innodb_flush_log_at_trx_commit=1
#sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
一個(gè)優(yōu)化好的從數(shù)據(jù)庫(kù)的配置文件如下：
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
[client]
port=3306
socket=/usr/local/mysql/mysql.sock
default-character-set=utf8
[mysqld]
sync_binlog=1
server-id=2
port=3306
socket=/usr/local/mysql/mysql.sock
pid-file=/home/mysql/temp/my3306.pid
user=mysql
datadir=/home/mysql/data
tmpdir=/home/mysql/temp/
log-bin=/home/mysql/data/mysqlslave-bin
log-error=/home/mysql/logs/error.log
slow_query_log_file=/home/mysql/logs/slow.log
binlog_format=mixed
slow_query_log
long_query_time=10
wait_timeout=31536000
interactive_timeout=31536000
max_connections=500
max_user_connections=490
max_connect_errors=2
character_set_server=utf8
skip-external-locking
key_buffer_size = 128M
max_allowed_packet = 5M
table_open_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 4
binlog-ignore-db=mysql
binlog-ignore-db=information_schema
replicate_ignore_db=mysql
replicate_ignore_db=information_schema
expire-logs-days=10
#skip-slave-start
skip-name-resolve
lower_case_table_names=1
log_bin_trust_function_creators=1
# InnoDB
innodb_data_home_dir=/home/mysql/data
innodb_log_group_home_dir=/home/mysql/logs
innodb_data_file_path=ibdata1:128M:autoextend
innodb_buffer_pool_size=2G
innodb_log_file_size=10M
innodb_log_buffer_size=8M
innodb_lock_wait_timeout=50
innodb_file_per_table
innodb_flush_log_at_trx_commit=1
#sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
sql_mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
[myisamchk]
key_buffer_size = 256K
sort_buffer_size = 256K
read_buffer = 256K
write_buffer = 256K
[mysqlhotcopy]
interactive-timeout
sql_mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
[myisamchk]
key_buffer_size = 256K
sort_buffer_size = 256K
read_buffer = 256K
write_buffer = 256K
[mysqlhotcopy]
interactive-timeout
總結(jié)
以上是生活随笔為你收集整理的mysql5.6 replication_MySQL5.6 Replication主从复制（读写分离) 配置完整版的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問(wèn)題。
- 上一篇： mysql linux 使用索引_正确使
- 下一篇： mysql数据库密码转换_MySQL数据