mysqldump SST cannot handle slow query log as a file
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL patches by Codership |
Fix Released
|
High
|
Alex Yurchenko | ||
| 5.1 |
Fix Released
|
High
|
Alex Yurchenko | ||
| 5.5 |
Fix Released
|
High
|
Alex Yurchenko | ||
Bug Description
If slow query log or general log have been configured to use files, then mysqldump based SST fails, with following error in the log:
ERROR 1146 (42S02) at line 2570: Table 'mysql.slow_log' doesn't exist
110926 16:32:31 [ERROR] WSREP: Process completed with error: wsrep_sst_mysqldump 'wsrep_sst' 'wsrep' '10.103.3.2' '3306' '3306' 'c5b4743e-
110926 16:32:31 [ERROR] WSREP: Try 1/3: 'wsrep_
How to reproduce:
use 2 nodes, and configure file base slow query log, in my.cnf write:
slow_query_log = 1
slow_query_log_file = /data/mysql/
Start node1 and node2 such that SST is needed to join node2.
| Changed in codership-mysql: | |
| status: | New → Confirmed |
| milestone: | none → 21.1 |
| importance: | Undecided → Low |
| Alex Yurchenko (ayurchen) wrote | #1 |
| Alex Yurchenko (ayurchen) wrote | #2 |
Further investigation shows that the problem is actually in that wsrep_sst_mysqldump cannot recreate mysql.slow_log table, which is present in the system schema by default. In a sense it is a database corruption: mysqldump SST simply loses the slow_log table.