This only works on MySQL 5.0. If you’re using 5.1+, this approach isn’t for you.
Today we had to do a very large alter table on some production data. The table in question is big. 47 million rows big. We have to make some changes to drop a column and change some indexing to support our application. Fine, ALTER TABLE blah blah blah. But how do we keep an eye on the progress of the alter?
There’s nothing in the documentation for MySQL that speaks to a method, nor does any google searching pull up anything (except for the one InnoDB file per table patch.)
So what’s a clever systems administrator to do?
I looked at the output of lots of status commands from MySQL, and finally I came across something useful in the InnoDB engine status output. I noticed that there was an entry in the TRANSACTION section that speaks to the undo log entries. I noticed that after several hours of our ALTER TABLE running that the undo log entries value was up around 33 million. And then it occurred to me that since InnoDB does row-level operations, that this value might correspond to the number of rows that have been operated on throughout the process of the ALTER:
So I wrote some bash. And some awk. And some perl, and I made a hacky little one-liner script to dump out the rate of change, the average rate of change, the % complete, and an estimate (based on average rate of change) as to when the query might be complete.
That script is below, and you are welcome to it. I have yet to wrap it in more clever perl to dump out an actual status bar, but I’m happy with it, and hopeful that this is a meaningful way of keeping an eye on the rate of change, and the progress of ALTER statements.
I hope you find this tool useful.
It took a LONG time for the query we performed to run, and it was very helpful to have this to gauge the time it’d take. The moving average is not the best for long-term accuracy; restart the script periodically for better views (and wait for ~100+ trips through the loop.)
It was within three minutes of accurate. It look a little longer than the script indicated (log undo entries was greater than the # of rows, but not by more than a small percentage (less than 0.01%.) The total query time was 22 hours, 9 minutes, and 33 seconds. So it was off by only 1 hundredth of a percent.
This is only valid for ALTER TABLE, but appears VERY useful.