Keep getting error: DeleteDuplicateIndexables – Error executing ‘query’ etc.

WPE support (after running the query on their end) says:

It did fail with error: ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query .

This can indicate that there is not enough memory available to run the query. This appears to be potentially related to the servers innodb buffer size but this is not something that we can increase on the server as it’s a set value. The only situations this value would increase would be if you were on a dedicated server and we upgraded to a larger server with a larger innodb buffer pool.

In this case it appears to be failing because the number of changes that are needed (large site, about 1600 products) is too much for the current server memory to handle. Due to this, Yoast may be able to offer a workable solution that could break the query up into smaller parts. However, of course, if you have a WP Cli command you’d like me to try I can absolutely give that a go!

That being said, the best way to approach this would likely be to reach out to Yoast to see if there is another manner in which this can be done or if there is a way that this query can be written to do this process in batches rather than all at once.

Clearly I’m not getting a VPS just to run a single query (pretty sure no one would)… so do you think you could maybe help out, by looking into this? (also considering you list them among your vetted hosting providers ?? )

• This reply was modified 4 years, 5 months ago by Duke.

Hi @dukessa,

Thank you for reaching out, we are sorry you are running into issues with these queries. The query itself is batched in 25 indexables at a time, but the query does indeed just continues.

However, for (extremely) large sites or sites that time out, we recommend doing nothing. I know it might sound strange but hear me out.

Yoast SEO will “lazy load” the new indexables feature as you, your authors, and your visitors read, write, and update content. In a few weeks, try running the site-wide scan again. If it still times out, you can continue to lazy load the content on your site until the process is low enough for your server resources or ask your server admin or web host to temporarily increase the timeout length while the process completes. Once it’s done, you should not need to do it again.

Hi @dukessa,

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new forum topic. Thank you!