MySQL Data Dumper

mydumper + myloader versus special mysql tables

Asked by CHANIAL David

Hi All,

I would like to know if it is a good idea to change the default behavior of mydumper or myloader to not dump/load mysql special tables like mysql.innodb_index_stats (eventually with an option --force-all-tables to avoid the filter).

This solution would avoid useless dumps, and avoid this kind of errors :

=============
** (myloader:24094): CRITICAL **: Error restoring mysql.innodb_index_stats from file mysql.innodb_index_stats.sql.gz: Duplicate entry 'dailysales-tSalesReportingConsult-PRIMARY-n_diff_pfx01' for key 'PRIMARY'

** (myloader:24094): CRITICAL **: Error restoring mysql.innodb_table_stats from file mysql.innodb_table_stats.sql.gz: Duplicate entry 'dailysales-tSalesReportingConsult' for key 'PRIMARY'
=============

I'm ready to make the patch myself and post it as a blueprint if you find that a good idea.

Please tell me your thought.

Question information

Language:
English Edit question
Status:
Expired
For:
MySQL Data Dumper Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Max Bubenick (max-bubenick) said : 		#1

Hi David, I think mydumper should skip those tables directly for now. Because they need an special care, i.e. drop and recreate at the end of the restore to make sense and not fail. Also Ive never faced a restore where those tables were important for the workload, can be some edge cases but ...

Revision history for this message
CHANIAL David (david-chanial) said : 		#2

> Hi David, I think mydumper should skip those tables directly for now.

Would you like i submit a patch for mydumper.c on this idea ?

> Because they need an special care, i.e. drop and recreate at the end of the restore to make sense and not fail. Also Ive never faced a restore where those tables were important for the workload, can be some edge cases but ...

No worlkload problem, just a theorical problem, useless dump of thoses special tables, and useless restore. Some "non-"understandable CRITICAL error. Why keep them if they can/should be avoided ?

Revision history for this message
Max Bubenick (max-bubenick) said : 		#3

Hi David, yes you can. But be aware that next release is being delayed as I hope to be based on lp:~max-bubenick/mydumper/mydumper-fss if I dont face any blocker. This one is introducing new features like full schema dump support.

Revision history for this message
Launchpad Janitor (janitor) said : 		#4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.