server_id
server_uuid
relay_log
io_thread read over local log.
relaylog file name prefix, it may be a full path.
relay_log_index
relaylog index file name prefix, and realy_log as may be fullpath.
It can not be modified dynamically.
read_only
Unless super authority, or you can not modify the data, but does not affect the autonomy to create temporary tables, ANALYZE TABLE, OPTIMIZE TABLE is not affected.
It can be dynamically modified.
replication_same_server_id
This parameter is not recommended.
skip_slave_start
Do not automatically start the synchronization database startup.
slave_load_tmpdir
Synchronous time to save the load data and the like data directory.
slave_transaction_retries
slave replication, because if InnoDB deadlock or lock timeout lead to transactional replication thread of execution failed retries.
It recommended keep the default.
slave_parallel_workers
The default is off
report_password
report_port
report_user
Prior to 5.7, if the three parameters mentioned above is not arranged, you can not use the show slave hosts;
Not recommended to configure the above parameters.
log_slow_slave_statements
Whether slave replication have produced slow log records.
It recommended that you turn
log_slave_updates
The master transmission over the change operation, the cost of re-recording the binlog, to do the second copy, as the total distribution nodes.
master_info_file/relay_log_info_file
Record relay log to-date information, master.info
max_relay_log_size
Relay_log size limit.
relay_log_purge
After the relay application, whether to automatically delete it immediately.
relay_log_recovery
When the slave Ben collapse or normal restart incompletely applied relay log is deleted, the new request is generated from the master binlog relay log again.
slave filter parameters:
Recommend filtering rules from the library settings, do not set at the main library.
replicate_do_table
replicate_ignore_table
replicate_rewrite_db
replicate_wild_do_table
replicate_wild_ignore_table
replicate_do_db
replicate_ignore_db
slave_net_timeout
slave_skip_erors
sql_slave_skip_counter
When the number of replication events ignored, individual encounters an error (primary key violation, records do not exist, etc.), can be ignored
These events continue the replication process.
Generally only once ignored an event, unless it is sure, do not set more than one.