Timeline for MySQL CPU usage super high since server crashed
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2018 at 21:04 | comment | added | Rick James | How many cores? | |
| Sep 20, 2018 at 21:03 | comment | added | Rick James | 5.5 is antique. Upgrade. You have 96GB of RAM? Yet very little is being used? | |
| Sep 2, 2018 at 0:21 | comment | added | Wilson Hauck | @johnv I AM a FREE support line. Additional information request, please. Post on pastebin.com or here. RAM size of your MySQL Host server A) complete (not edited) my.cnf or my.ini Text results of: B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) complete MySQLTuner report if readily available - 7 or more days uptime is helpful E) SHOW ENGINE INNODB STATUS; F) SELECT name, count FROM information_schema.innodb_metrics ORDER BY name; Optional very helpful information, if available includes - htop OR top OR mytop for most active apps, | |
| Aug 28, 2018 at 23:59 | comment | added | Wilson Hauck | @johnv Please look in chat for requested information. There are likely some global variables needing attention that will be discovered with your GLOBAL STATUS and GLOBAL VARIABLE information. All SWAP space was in use, with ~ 96GB of RAM, be liberal with your swap space, 128M might be reasonable to survive the unpredictable. Please view my profile, Network profile for contact information including my Skype ID and get in touch with me. | |
| Aug 26, 2018 at 13:45 | comment | added | John V | Let us continue this discussion in chat. | |
| Aug 26, 2018 at 13:29 | comment | added | peterh | @JohnV There is mysql-slow.log or similar, you can set it in the my.cnf. That logs the queries which were too long. | |
| Aug 26, 2018 at 13:25 | comment | added | peterh | @JohnV It is a "tip of iceberg" problem now, we can answer questions but can't debug your system. Cron has most likely nothing to do that. If you have still problems, ask new questions. | |
| Aug 26, 2018 at 12:35 | comment | added | John V | I stopped all cronjobs that I had (crons with queries) and CPU usage is 0% now, so it's still a database problem... I'll check which tables are using those crons and try to figure out whats going on... because I dumped all those tables and the problem is still there. | |
| Aug 26, 2018 at 11:41 | comment | added | peterh | @JohnV Btw, other database engines have much lesser problems. Maybe you could try postgresql. | |
| Aug 26, 2018 at 11:40 | comment | added | peterh | @JohnV Then reinitalize the whole thing (remove mysql, delete /var/lib/mysql, install mysql). | |
| Aug 26, 2018 at 10:53 | comment | added | John V | Do I need to delete all databases before the import? i did it without delete them and the problem persist. | |
| Aug 26, 2018 at 10:39 | history | edited | peterh | CC BY-SA 4.0 |
added 1 character in body
|
| Aug 26, 2018 at 10:38 | comment | added | John V | Thank you, i'm gonna try that. I've daily backups of my databases. Hope it works! I just tried to repair all tables & databases but nothing changed, let's see. | |
| Aug 26, 2018 at 10:35 | history | answered | peterh | CC BY-SA 4.0 |