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

Version: 5.6.16

A problem is seen in the group. When backing up, the following error is reported:

[root@B28-19-75 bak] # mysqldump-root-p-single-transaction-- master-data=2-- databases db1 db2 db3 db4 db5 > db.sql

Mysqldump: Error 1882: Query execution was interrupted, max_statement_time exceeded when dumping table `admin_operation_ log` at row: 760155

My max_statement_time parameter is not set in the configuration file, by default. Group friends set up max_statement_time=500.

Max_statement_time function:

Function: it is used to control the maximum execution time of the query in MySQL. If the setting time of this parameter is exceeded, the query will fail automatically. The default is unlimited.

Suggestion: if you want to control the execution time of SQL in the database, you can enable this parameter (in milliseconds).

Phenomenon: ERROR 1882: Query execution was interrupted, max_statement_time exceeded

Modify the parameter values:

Mysql > set session max_statement_time = 0

Query OK, 0 rows affected (0.00 sec)

Mysql > show variables like'% max_statement%'

+-+ +

| | Variable_name | Value |

+-+ +

| | max_statement_time | 0 | |

| | performance_schema_max_statement_classes | 179 |

+-+ +

Backup again, do not report an error:

[root@B28-19-75 bak] # mysqldump-root-p-single-transaction-- master-data=2-- databases db1 db2 db3 db4 db5 > db.sql

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.