Hi all,
Started a conversion from MyISAM to InnoDB; it's been almost two days and the
statement is still executing...
The (MyISAM) data table size is almost 4G. There were two reasons for this conversion:
to start supporting transactions and to avoid the 4G limit of MyISAM tables; this
table has been created without explicitly specifying MAX_ROWS and AVG_ROW_LENGTH.
The avg row length is 28 bytes, there's only a primary key comprised of 3 integers.
The state of this thread that's performing the conversion is "Copy to tmp table".
We need to start updating the table as soon as possible...
Is there a way to monitor the progress?
Is the tmp table allocated in InnoDB tablespace?
What are the consequences of killing the thread? Will it waste whatever InnoDB
tablespace has been already used for this conversion?
I'm using Mysqlcc. How long may it take to cancel this statement by pushing "Cancel
execution and clear
results" button? Sometimes it takes a while... What does this button actually do?
Thanks in advance for your help!
-- Sergei
