中继日志

中继日志来自Master的二进制日志， I / O线程从Master读取，然后写入本地的一类日志，类似于binary log。作为SQL线程的输入，中继日志中的事件将通过SQL线程来重演，从而实现复制。

The relay log consists of the events read from the binary log of the master and written by the slave I/O thread. Events in the relay log are executed on the slave as part of the SQL thread.

相关的参数：
mysql> show variables like '%relay%'; 
+-----------------------+----------------+ 
| Variable_name | Value | 
+-----------------------+----------------+ 
| max_relay_log_size | 0 | 
| relay_log | | 
| relay_log_index | | 
| relay_log_info_file | relay-log.info | 
| relay_log_purge | ON | 
| relay_log_recovery | OFF | 
| relay_log_space_limit | 0 | 
| sync_relay_log | 0 | 
| sync_relay_log_info | 0 | 
+-----------------------+----------------+

sync_relay_log

• Description: The MariaDB server will synchronize its relay log to disk after this many writes to the log. The default until MariaDB 10.1.7 was 0, in which case the operating system handles flushing the file to disk. 1 is the safest, but slowest, choice, since the file is flushed after each write. If autocommit is enabled, there is one write per statement, otherwise there's one write per transaction. If the disk has cache backed by battery, synchronization will be fast and a more conservative number can be chosen.
• Commandline: --sync-relay-log=#
• Scope: Global
• Dynamic: Yes
• Data Type: numeric
• Default Value: 10000 (>= MariaDB 10.1.7), 0 (<= MariaDB 10.1.6)

sync_relay_log_info和sync_relay_log类似

relay_log_purge

• Description: If set to 1 (the default), relay logs will be purged as soon as they are no longer necessary.
• Commandline: --relay-log-purge={0|1}
• Scope: Global
• Dynamic: Yes
• Data Type: boolean
• Default Value: ON
  
  完整的参数可以参考。
  https://mariadb.com/kb/en/library/replication-and-binary-log-server-system-variables/#relay_log_purge
  

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/29497382/viewspace-2153357/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/29497382/viewspace-2153357/