content_image/688489.jpg
Closes and reopens any binary log file to which the server is writing. If binary logging is enabled, the sequence number of the binary log file is incremented by one relative to the previous file. 

This operation requires the RELOAD  privilege. 

• FLUSH ENGINE LOGS 

Closes and reopens any flushable logs for installed storage engines. This causes InnoDB  to flush its logs to disk. 

This operation requires the RELOAD  privilege. 

• FLUSH ERROR LOGS 

Closes and reopens any error log file to which the server is writing. 

This operation requires the RELOAD  privilege. 

• FLUSH GENERAL LOGS 

Closes and reopens any general query log file to which the server is writing. 

This operation requires the RELOAD  privilege. 

This operation has no effect on tables used for the general query log (see Section 5.4.1, “Selecting General Query Log and Slow Query Log Output Destinations” ). 

• FLUSH HOSTS 

Empties the host cache and the Performance Schema host_cache  table that exposes the cache contents, and unblocks any blocked hosts. 

This operation requires the RELOAD  privilege. 

For information about why host cache flushing might be advisable or desirable, see Section 5.1.12.3, “DNS Lookups and the Host Cache” . 

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

• FLUSH LOGS 

Closes and reopens any log file to which the server is writing. 

This operation requires the RELOAD  privilege. 

## Note 

FLUSH HOSTS  is deprecated as of MySQL 8.0.23; expect it to be removed in a future MySQL release. Instead, truncate the Performance Schema host_cache table: 

TRUNCATE TABLE performance_schema.host_cache; 

The TRUNCATE TABLE  operation requires the DROP  privilege for the table rather than the RELOAD  privilege. 

The effect of this operation is equivalent to the combined effects of these operations: 

FLUSH BINARY LOGS FLUSH ENGINE LOGS 

