In the last couple of days I've have my connection count to MySQL go above a set threshold of 35 sometimes peaking at over 150. When this happens SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS are ran so I can investigate what is causing the issue. After looking it over it appears that TRUNCATE cache_field is causing the issue. Looking over the options it appears that TRUNCATE commands need to not be ran on a live table. This means we need to rename the table before the truncate happens.
http://bugs.mysql.com/bug.php?id=61935#c368453
http://stackoverflow.com/questions/17762361/truncate-table-taking-very-l...
http://dba.stackexchange.com/questions/20600/what-can-cause-truncate-tab...
http://whatwebwhat.com/en/page/466/truncating-big-mysql-innodb-tables
Closed: outdated
9.5
It affects performance. It is often combined with the Needs profiling tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Drupal requires MySQL 5.7 now, so I believe this is resolved by https://bugs.mysql.com/bug.php?id=68184
Closing as outdated.
🐛 The truncate method is does different things on different databases and depending if in a transation Closed: outdated is still open for some of the other issues.