Hello Team,
Please
let me know , if you need any other details. A
The table_rows in the information_schema.TABLE for innodb is purely and estimate. I doubt you are missing actual rows. The estimate gather by the different implementation, or even different server depending on how they are loaded can generate significant differences of the order of magnitude presented here. Check using the slower SELECT COUNT
FROM table. Maybe pt-table-checksum can help verify table contents for the higher degree of certainty you need.
While focal does have a 10.3 version, as far as upstream here is concerned its eol.
I recommend bumping to the jammy 10.6 version to ensure a common distro and upstream maintaince.
Hello @Daniel Black,
Thank you very much for your valuable points. Yes, we have checked row counts in all tables. That also given different result. And even database size also differed from mysql.In mysql the total size of the DB is 9.4GB but in restored mariadb the database size is 8.7GB.
Additionally , I will try with Maria DB 10.6 (Jammy ) and I will update you back. Thanks once again.
Hello @Daniel Black,
I have tried with mariadb10.6. But there is no luck, same issue in mariadb10.6 also.
How are you doing the backup/restore? The size on disk can be naturally smaller on a logical restore. What table content method is being used to determine accuracy of migration? I see you've marked Replication - is the 10.6 instance a replica of the 5.7 master? If so pt-table-sync can check and fix replica consistency.
Basically I'm migrating from mysql5.7 to mariadb . The total number of rows in tables is differ in mysql and mariadb.
For mysql backup used below command:
mysqldump -u username -p --databases database > database.sql
To restore that mysql dump in maria DB , I have used below query.(After logging into mariadb used below query to restore)
source /path/database.sql;
I have used below query to check the total number of rows in a table
SELECT COUNT FROM table_name;
Hello Team,
Please update on this, this case is now getting serious as Ubuntu 18.04 support is going to terminate its support by 31 Maay 2023(EOL).
Are you willing to share your dump privately for testing on our ftp service?
Hello Daniel,
As this is a production environment , I cannot share the dump to outside. If possible can we connect and discuss?
Can you import the data into a fresh 5.7 instance and verify the counts match those from the origin? How do they compare to the mariadb instance?
Can you include SHOW GLOBAL STATUS and SHOW ENGINE INNODB STATUS from the MySQL-5.7 and MariaDB-10.6 side by side after the install?
If still differences;
Are the primary/unique keys of tables of text/char/varchar types of differing collations?
Hello Daniel,
Thanks for your concerns, This issue got resolved.The information_schema gives the assumed values of row_counts. We need to check the row counts for each tables using select count table_name.
Great to hear. Wishing you a stable migration when the time comes.
Hello @Daniel Black,
Thanks for your valuable points. We have done the migration without any issues.