Mysql
MySQL Master-Master 複製不同步
設置：
為了安全起見，我在 2 台機器上設置了 WAMP MySQL Master-Master 複製設置，sync_binlog=1。機器配置：Windows Azure Standard 2：2 核，4GB RAM，Windows Server 2008，MySQL 5.6.12，WAMP 2.4
問題：
如果我在前 5-10 分鍾啟動奴隸，一切都很好。在此之後，我的插入\更新將永遠不會在兩個數據庫中同步。如果我選中“顯示從屬狀態\G”：
Slave_IO_State: Waiting for master to send event Last_Errno: 0 Last_Error: Last_IO_Errno: 0 Last_IO_Error: Last_SQL_Errno: 0 Last_SQL_Error: 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如果我做“停止奴隸\啟動奴隸”機器同步。
題：
解決這個問題的正確方法是什麼，或者我設置錯誤的參數是什麼？
//稍後編輯這是我的2個mysql.ini
大師1：
# The MySQL server [wampmysqld] socket = /tmp/mysql.sock key_buffer = 16M max_allowed_packet = 1M sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M basedir=c:/wamp/bin/mysql/mysql5.6.12 log-error=c:/wamp/logs/mysql.log datadir=c:/wamp/bin/mysql/mysql5.6.12/data # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the "enable-named-pipe" option) will render mysqld useless! # #skip-networking # Disable Federated by default skip-federated # Replication Master Server (default) # binary logging is required for replication #log-bin=mysql-bin # binary logging format - mixed recommended binlog_format=mixed # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 log_bin = binlog log_bin_index = binlogindex relay_log = relaylog relay_log_index = relaylogindex log_slave_updates = 1 auto-increment-increment = 2 auto-increment-offset = 1 sync-binlog = 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - # the syntax is: # # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>, # MASTER_USER=<user>, MASTER_PASSWORD=<password> ; # # where you replace <host>, <user>, <password> by quoted strings and # <port> by the master's port number (3306 by default). # # Example: # # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, # MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then # start replication for the first time (even unsuccessfully, for example # if you mistyped the password in master-password and the slave fails to # connect), the slave will create a master.info file, and any later # change in this file to the variables' values below will be ignored and # overridden by the content of the master.info file, unless you shutdown # the slave server, delete master.info and restart the slaver server. # For that reason, you may want to leave the lines below untouched # (commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id = 2 # # The replication master for this slave - required #master-host = <hostname> # # The username the slave will use for authentication when connecting # to the master - required #master-user = <username> # # The password the slave will authenticate with when connecting to # the master - required #master-password = <password> # # The port the master is listening on. # optional - defaults to 3306 #master-port = <port> # # binary logging - not required for slaves, but recommended #log-bin=mysql-bin # Point the following paths to different dedicated disks #tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = C:\mysql\data/ #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = C:\mysql\data/ #innodb_log_arch_dir = C:\mysql\data/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 1024M innodb_additional_mem_pool_size = 20M bulk_insert_buffer_size = 256M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 5M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout [mysqld] innodb_file_per_table max_connections = 300 innodb_read_io_threads = 64 innodb_thread_concurrency = 0 innodb_write_io_threads = 64 sync-binlog = 1 sync-relay-log = 1 sync-relay-log-info = 1 sync-master-info = 1大師2：
# The MySQL server [wampmysqld] socket = /tmp/mysql.sock key_buffer = 16M max_allowed_packet = 1M sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M basedir=c:/wamp/bin/mysql/mysql5.6.12 log-error=c:/wamp/logs/mysql.log datadir=c:/wamp/bin/mysql/mysql5.6.12/data # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the "enable-named-pipe" option) will render mysqld useless! # #skip-networking # Disable Federated by default skip-federated # Replication Master Server (default) # binary logging is required for replication #log-bin=mysql-bin # binary logging format - mixed recommended binlog_format=mixed # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 2 log_bin = binlog log_bin_index = binlogindex relay_log = relaylog relay_log_index = relaylogindex log_slave_updates = 1 auto-increment-increment = 2 auto-increment-offset = 2 sync-binlog = 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - # the syntax is: # # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>, # MASTER_USER=<user>, MASTER_PASSWORD=<password> ; # # where you replace <host>, <user>, <password> by quoted strings and # <port> by the master's port number (3306 by default). # # Example: # # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, # MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then # start replication for the first time (even unsuccessfully, for example # if you mistyped the password in master-password and the slave fails to # connect), the slave will create a master.info file, and any later # change in this file to the variables' values below will be ignored and # overridden by the content of the master.info file, unless you shutdown # the slave server, delete master.info and restart the slaver server. # For that reason, you may want to leave the lines below untouched # (commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id = 2 # # The replication master for this slave - required #master-host = <hostname> # # The username the slave will use for authentication when connecting # to the master - required #master-user = <username> # # The password the slave will authenticate with when connecting to # the master - required #master-password = <password> # # The port the master is listening on. # optional - defaults to 3306 #master-port = <port> # # binary logging - not required for slaves, but recommended #log-bin=mysql-bin # Point the following paths to different dedicated disks #tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = C:\mysql\data/ #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = C:\mysql\data/ #innodb_log_arch_dir = C:\mysql\data/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 1024M innodb_additional_mem_pool_size = 20M bulk_insert_buffer_size = 256M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 5M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout [mysqld] innodb_file_per_table max_connections = 300 innodb_read_io_threads = 64 innodb_thread_concurrency = 0 innodb_write_io_threads = 64 sync-binlog = 1 sync-relay-log = 1 sync-relay-log-info = 1 sync-master-info = 1
問題
在 Windows 中刷新到磁碟時，MySQL 需要非常明確。當你這樣做時，你已經抓住了這一點
STOP SLAVE;，並且START SLAVE;你說你正在使用sync-binlog = 1。那太好了。這只解決了一半的日誌文件問題。
解決方案（或至少建議）
您需要同步所有其他複製組件
[mysqld] sync-binlog = 1 sync-relay-log = 1 sync-relay-log-info = 1 sync-master-info = 1SQL 執行緒從中繼日誌中讀取 master 的 binlog events。執行 sync-binlog 只會刷新主日誌。通過刷新中繼日誌和相關的複制狀態文件，這應該可以更準確地從中繼日誌中讀取複製狀態和二進制日誌事件。
這是這些選項的 MySQL 文件
試一試 ！！！
CAVEAT：可能對磁碟 I/O 有很小的影響。請監視它。
在您的從屬my.cnf文件中嘗試該選項：slave-net-timeout = 60
（在從站認為連接斷開、中止讀取並嘗試重新連接之前，等待來自主站的更多數據或心跳信號的秒數。）
我使用 MariaDB (<= MariaDB 10.2.3)，預設值為 3600 (sec)。
現在我的數據庫已同步。