-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Schema index checksum mismatch found! #862
Comments
Hi @fazi1058, can you share the SHOW CREATE TABLE from the database you exported and the database you imported? |
I am afraid I can't share table structure with you but when I ran query the only difference between them was auto_increment:
first one belongs to the database I imported and second one belongs to database I got export from. |
Can you execute this on both databases: With the right |
Definitely this is a duplicate of #860, sorry for the back and forth... |
It is still not working properly |
@fazi1058 please, share a test case so I can work on this before the next release. |
Hello!
I am using myloader and mydumper for taking bakup and restore them.But when I restore backup I encounter with errors below:
** (myloader:2868268): WARNING **: 10:04:25.349: Schema index checksum mismatch found for `db_name`.`orders`. Got '83671d4e', expecting 'CB0C64DE' in file: db_name.orders-schema-indexes-checksum
** (myloader:2868268): WARNING **: 10:04:24.369: Schema index checksum mismatch found for `db_name`.`demo__orders`. Got '40fd4431', expecting '160AD7C6' in file: db_name.demo__orders-schema-indexes-checksum
My question is that : Should I be worried? because all checksum for data and their schema was OK except these two! How does it effect? How it is happening?
mydmper command:
mydumper --database=$DB_NAME --user=$DB_USER --outputdir=/Backup/$DB_NAME--$DATE --build-empty-files --trx-consistency-only --compress --checksum-all
myloader command:
myloader -t 32 -d db_name --serialized-table-creation --verbose 3 -B db_name
The text was updated successfully, but these errors were encountered: