Shulou(Shulou.com)06/01 Report--

max_relay_log_size: the maximum value allowed for the tag relay log. If the value is 0, the default value is max_binlog_size(1G); if it is not 0, max_relay_log_size is the maximum relay_log file size;

relay_log： By default, relay log file names have the form host_name-relay-bin. nnn in the data directory;

relay_log_index: Same as relay_log, defines the location and name of relay_log;

relay_log_info_file: Sets the location and name of relay-log.info (relay-log.info records the recovery location of binary_log of MASTER and the location of relay_log)

relay_log_purge: Whether to automatically purge the relay log when it is no longer needed. The default value is 1(enabled).

relay_log_recovery: When the slave goes down from the library, if the relay-log is damaged, resulting in some relay logs not being processed, all unexecuted relay-logs will be automatically discarded and logs will be retrieved from the master again, thus ensuring the integrity of the relay-log. By default, this function is off. When relay_log_recovery is set to 1, this function can be enabled on slave slave library. It is recommended to enable it.

relay_log_space_limit: Prevent relay logs from filling disk. Set maximum relay log limit here. However, this setting has the main library crash, from the library relay log incomplete situation, not recommended unless absolutely necessary;

sync_relay_log: This parameter is the same as sync_binlog. When it is set to 1, the slave I/O thread writes the binlog log sent by the master to the system buffer every time it receives it, and then brushes it into the relay log relay log. This is the safest way, because when you crash, you will lose at most one transaction, but it will cause a lot of I/O to the disk. When set to 0, it is not immediately flushed into the relay log, but the operating system decides when to write, although security is reduced, but a large number of disk I/O operations are reduced. This value defaults to 0 and can be modified dynamically. It is recommended to use the default value.

sync_relay_log_info： This parameter is the same as sync_relay_log parameter. When set to 1, every time slave I/O thread receives binlog from master, it will write it to system buffer and then brush it into relay-log.info. This is the safest way, because in the case of crash, you will lose at most one transaction, but it will cause a lot of I/O to disk. When it is set to 0, it is not immediately flushed into relay-log.info, but the operating system decides when to write, although security is reduced, but a large number of disk I/O operations are reduced. This value defaults to 0 and can be modified dynamically. It is recommended to use the default value.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.