Killed Query Error – class-queue-storage-options.php:129

  • Resolved tplomari

    (@tplomari)


    2 years, 6 months ago

    I am periodically getting a KILLED QUERY error in WP Engine due to the below query. Any way to mitigate besides overriding WP Engine’s query cap (I’m not trying to add any performance issues to our multisite right now)? Is Jetpack/Automattic reviewing this as an issue already?

    KILLED QUERY (20052 characters long generated in /nas/content/live/caen/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/sync-queue/class-queue-storage-options.php:129)

    I’m using the following versions:

    • Jetpack 12.6
    • Php 8 (prod) & 8.2 (dev)
    • WordPress 6.3.1

    Thanks for any input.

    • This topic was modified 2 years, 6 months ago by tplomari. Reason: Added version info
Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter tplomari

    (@tplomari)

    2 years, 6 months ago

    Update: it looks like there were up to 1,000 rows in wp_options with option_name containing jpsq_sync for the sites in which we received the above mentioned error. I’m still unsure of why that happened, but deactivating and reactivating cleared the massive number of rows of those options for now. Would love to know why this occurred to begin with! Thanks!

    mindtakerminis

    (@mindtakerminis)

    2 years, 5 months ago

    Just ran into this myself. I deactivated Jetpack but it didn’t clear the rows, so I had to remove them manually in phpmyadmin. We’ll see how badly I broke things.

    Thread Starter tplomari

    (@tplomari)

    2 years, 5 months ago

    @mindtakerminis – interesting, when I deactivated through the admin dashboard, reactivated, then reconnected Jetpack, the massive number of jpsq_sync rows in the options table went completely away….So far for the sites for which I’ve done this they’ve not returned. But the fun part is that I managed a multisite of almost 400 sites so manually doing this for each of them is NOT ideal…and I am really hoping to understand what caused it bc I don’t want to ever deal with this again. 174,000 rows of needless data across my dang multisite. C’mon now. Eesh. I’ll post back here if I figure out the source of it.

    mindtakerminis

    (@mindtakerminis)

    2 years, 5 months ago

    Ope, and it’s filling back up. 2k lines and counting.

    mindtakerminis

    (@mindtakerminis)

    2 years, 5 months ago

    I think the difference may have been that I deactivated the plugin instead of disconnecting JP through JP Settings.

    Thread Starter tplomari

    (@tplomari)

    2 years, 5 months ago

    Noooo! Have you tried disconnecting and reconnecting the Jetpack connection (not the plugin activation)?

    mindtakerminis

    (@mindtakerminis)

    2 years, 5 months ago

    Yeah, I did that the second time which did clear out the rows but now it seems to be reoccurring. May be time for me to create my own thread.

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    2 years, 5 months ago

    Hi @mindtakerminis I see you started your own thread on this, so we’ll reply there, and I will close this thread.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Killed Query Error – class-queue-storage-options.php:129’ is closed to new replies.