While seeding a bunch of new slaves for an infrastructure (and
after I had successfully seeded and started replication on
several, and I can verify that the database is consistent), one
of my fellow DBAs checks the mysql error log and says “INNODB
CORRUPTION!!”.
All of my servers were spewing these errors.
2018-05-09T10:29:10.420943-05:00 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2018-05-09T10:29:10.421717-05:00 0 [ERROR] InnoDB: Page [page id: space=XXXX, page number=XXXXXXXX] log sequence number XXXXXXXXXXX is in the future! Current system log sequence number XXXXXXXXX.
But — No. I do not have InnoDB corruption in this
case. I discovered a brand new gripe with MySQL &
InnoDB. This is not a ‘bug’ but more …
[Read more]