Elementor update causes database freeze-up
On Nov 9 and Nov 23, as part of regular maintenance updates, I tried updating Elementor from version 3.4.4 to the latest version (3.4.6 or 3.4.8). Both times, the Commons database was brought to a halt by an influx of database connections, within minutes.
Effective immediately, I won't be updating Elementor anymore during regular maintenance updates. Specifically, I will add it to the list of blocked plugins in my wp-cli-cac update tools. Ray, if you have your own version of these tools, please do the same.
The next time Elementor is updated to a new major version, say 3.5, I might consider trying the update again in isolation. I'll leave this ticket open for further investigation.
#1 Updated by Boone Gorges 2 months ago
A possible clue is that the mysql processlog shows many entries during these incidents that look like this:
1220 commons_admin 220.127.116.11:59488 commons_wp Sleep 284 NULL 1713 1713 1221 commons_admin 18.104.22.168:59494 commons_wp Sleep 211 NULL 1713 1713 1222 commons_admin 22.214.171.124:59498 commons_wp Sleep 291 NULL 1713 1713
Some query is taking place that matches 1713 rows. At one point I had the idea to see which tables in the Commons database have 1713 rows, but this is a much harder thing to query than you might expect.
#4 Updated by Raymond Hoh 2 months ago
Here's the changelog between Elementor v3.4.4 and v3.4.6: https://github.com/elementor/elementor/compare/v3.4.4...v3.4.6The only commits that stand out are:
The first one seems likely because Elementor is doing a save routine on every page load. Just a guess though.