wsrep_sst_mysqldump drops mysql.slow_log table on joiner

Bug #609259 reported by Alex Yurchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
Medium
Teemu Ollakka
0.7
Fix Released
Medium
Teemu Ollakka
Trunk
Fix Released
Medium
Teemu Ollakka

Bug Description

mysqdump does not seem to be able to replicate mysql.slow_log table (perhaps because of the CSV storage engine), but it drops mysql database on joiner before creating new tables. This make it impossible to use slow query logging.

Changed in codership-mysql:
importance: Undecided → Medium
milestone: none → 0.8
status: New → Confirmed
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

Dump created from mysql databasde with mysqldump --add-drop-database, cannot be loaded back in MySQL. Reason is that both general query log and slow query log tables (which are of CSV engine type), will not be re-created during the loading.

One workaround is to disable CSV engine altogether. Then general_log and slow_log would not be used at all.

Here we however fix this by (a workaround), where wsrep_sst_mysqldump will fix the joiner's mysql database after the dump is loaded.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.