CODEWITHSUNDEEP
mysqlinnodbrollback
James Glass
James Glass

Reputation: 4300

Will killing a large InnoDB rollback hurt my tables?

Using phpMyAdmin's "Copy Database" feature, I started copying one database with ~5M rows to another on the same server. About halfway through (2 hours or so) the server started crashing, and I had to kill the mysqld process.

MySQL is killing my server right now trying to roll back the tables that it had already started before I killed the process. It's been running for over 50 minutes now and slowing everything down.

Using show engine innodb status I was able to find the process no. Should I kill this process? Will it hurt my tables, or hurt anything, or is it safe to stop the rollback?

Here's the entry. At it's current rate, it looks like it'll take about 3 more hours to finish the 983k log entries left.

---TRANSACTION 0 1853619464, ACTIVE 3214 sec, process no 5552, OS thread id 3028249488 ROLLING BACK , undo log entries 983813

Upvotes: 0

Views: 4130

Answers (1)

user1549550
user1549550

Reputation:

If you kill your rollback, it'll just do the rollback again the next time. It must complete the rollback to get the tables back to a consistent state.

Upvotes: 3

Related Questions