Note: This issue has been fixed in MySQL 8.0.0, 14 years after the original bug report.
Few weeks ago I hit an interesting bug in production that made me wonder is time-travel real!? I was seeing activities for emails before the emails were actually sent…
How is that even possible I was wondering!?
It turns out, InnoDB does not persist the auto-increment counter on disk.
If you specify an AUTO_INCREMENT column for an InnoDB table, the table handle in the InnoDB data dictionary contains a special counter called the auto-increment counter that is used in assigning new values for the column. This counter is stored only in main memory, not on disk.
To initialize an auto-increment counter after a server restart, InnoDB executes the equivalent of the following statement on the first insert into a table containing an AUTO_INCREMENT column.
SELECT MAX(ai_col) FROM table_name FOR UPDATE;
After reading the above documentation, I had a light-bulb moment.
I have one temporary table in the system that is regularly cleaned removing old unnecessary data to take care of disk space usage. It’s a multi-tenant architecture in which each user has it’s own database and when user is inactive for a period of time, one of their tables becomes empty after cron task deletes data.
One of the physical servers running few MySQL instances was having memory issues that caused some instances to restart. After restart, the
AUTO_INCREMENT value for the empty table got reset to 0 and newly inserted records were with IDs that were already used.
Knowing the issue, the solution is pretty straight-forward. When cleaning the table, leave the last record in there, so that if server crashes and restarts again, the
AUTO_INCREMENT value will get initialized to the correct value instead of getting reset to 0.
Fixing the incorrect
AUTO_INCREMENT counters for the table involves figuring out a safe max INT value based on relations that the table has with other tables in the database and changing it. Also, a dummy record needs to be inserted in cleaned empty tables to prevent the issue from happening again if server crashed again before new data is inserted in the table.
To get the auto-increment value for a table:
SELECT AUTO_INCREMENT FROM information_schema.tables WHERE table_name = 'table_name' AND table_schema = DATABASE();
To set the auto-increment value for a table:
ALTER TABLE table_name AUTO_INCREMENT = new_value;
It’s surprising to learn about this
AUTO_INCREMENT behaviour with InnoDB that is unexpected in my opinion. It’s even more surprising when it comes after a year in production, but that’s just because the database servers and application have been rock solid in general. Luckily, it was an isolated case and was fixed quickly to prevent further data damage that will require more serious data fix. Just something to be aware of and design around this flaw to prevent it bite you.