I have a replicated database setup, mostly Innodb databases/tables. The query that I believe caused the issue ran in about 20 minutes on the master database. This is where it gets weird. Show processlist has nothing listed, except for my connection and the replicant connection. Innodb has a transaction running according to show innodb status. The transaction has been running for 7+ hours.
Replication seems to have stopped, despite the slave_io and slave_sql both running. The Exec_Master_Log_Pos hasn't budged and cpu usage is at 100% (1 core).
Is there any way to see what query it's actually running as well as maybe a way to figure out how long the transaction may take? I'm kind of lost here and about to blow away the slave and resetup replication if I can't get anywhere soon.