content_image/765727.jpg content_image/765728.jpg content_image/765736.jpg
• --max-binlog-dump-events= N 

<img src='content_image/765727.jpg'>

This option is used internally by the MySQL test suite for replication testing and debugging. 

• --sporadic-binlog-dump-fail 

<img src='content_image/765728.jpg'>

This option is used internally by the MySQL test suite for replication testing and debugging. 

## System Variables Used with Binary Logging 

The following list describes system variables for controlling binary logging. They can be set at server startup and some of them can be changed at runtime using SET . Server options used to control binary logging are listed earlier in this section. 

• binlog_cache_size 

<img src='content_image/765736.jpg'>

The size of the memory buffer to hold changes to the binary log during a transaction. The value must be a multiple of 4096. 

When binary logging is enabled on the server (with the log_bin  system variable set to ON), a binary log cache is allocated for each client if the server supports any transactional storage engines. If the data for the transaction exceeds the space in the memory buffer, the excess data is stored in a temporary file. When binary log encryption is active on the server, the memory buffer is not encrypted, but (from MySQL 8.0.17) any temporary file used to hold the binary log cache is encrypted. After each transaction is committed, the binary log cache is reset by clearing the memory buffer and truncating the temporary file if used. 

If you often use large transactions, you can increase this cache size to get better performance by reducing or eliminating the need to write to temporary files. The Binlog_cache_use  and 

