greg_repolitic Posted November 29, 2022 Share Posted November 29, 2022 I recently tried to do a Innodb conversion on a rather large table. I didn't' realize it was as large as it was - 1.5M rows. I used phpmyadmin to execute the query... which I now realize was a mistake. I got a timeout error after a min or so. Now I'm seeing extremely high CPU, and mysql is consuming 50%+ CPU and 35% + memory. What should I do? Just let this run out, or reboot and try again via the command line? I've placed the community into maintenance mode for now. Thanks! Link to comment Share on other sites More sharing options...
greg_repolitic Posted November 29, 2022 Author Share Posted November 29, 2022 Ok, a quick update on what's happened between when I posted above and now... I've looked at the database, and now all the tables are correctly showing as Innodb (not MyISAM), which is good! However, I'm still seeing VERY high load and memory usage. So should I wait, or reboot. Is there anything else anyone would recommend I do at this point? Thanks~! Link to comment Share on other sites More sharing options...
balazsp Posted November 29, 2022 Share Posted November 29, 2022 @greg_repolitic It is possible that the timeout was from the webserver and the mysql command is still running. You can check it in a new phpmyadmin window under status > processes: It will list the running mysql commands. If the conversion query is still running there then you should wait until it is completed. greg_repolitic 1 Link to comment Share on other sites More sharing options...
teraßyte Posted November 30, 2022 Share Posted November 30, 2022 It's better to run queries on such big tables from SSH rather than phpMyAdmin. greg_repolitic 1 Link to comment Share on other sites More sharing options...
Recommended Posts