1, parameter view
Method a: mysql> show variables like 'slave_pending_jobs_size_max ';
Method two: directly access parameter value my.cnf file slave_pending_jobs_size_max
2, parameter configuration
method:
stop slave;
set global slave_pending_jobs_size_max=250000000;
start slave;
Use my.cnf parameters will be lost after the restart
Method Two: innodb_flush_log_at_trx_commit directly modify the parameter values my.cnf file, but need to restart the instance of the entry into force
3, meaning the value of the parameter
When multi-threaded replication, the maximum memory queue Pending events occupied, the default is 16M, if memory surplus, or large delay may be appropriately adjusted large; Note that this value is greater than the need to max_allowed_packet main library.
4, the outer material
often encountered when adjusted synchronous replication slave SQL thread filing error according to the situation as follows:
Last_Errno: 1864
Slave_SQL_Running: No
Last_Error: Cannot schedule event Write_rows, relay-log name ./mysql-relay-bin.001304, position 416228895 to Worker thread because its size 16777357 exceeds 16777216 of slave_pending_jobs_size_max.
Because slave_pending_jobs_size_max less than the current size of the event you need to perform the required memory size.
5, the official website information