• Resolved mikacns

    (@mikacns)


    Hey,

    I tested the plugin on staging and managed to Add high performance keys, but when I tried to convert keys to the plugin’s high-performance keys it timed out after a couple of minutes. There are over 10 million rows in wp_postmeta so that’s understandable.

    The problem is that after it times out, the option to convert to high performance keys disappears, as if it performed the operation correctly. Can this corrupt the data, since the operation timed out in the middle of converting? I am reluctant to try this out on the production website for this reason. I will try to perform the operation on staging via WP-CLI in the meantime.

    I also uploaded the monitor result, the ID is HGqhqGgb if that helps.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author OllieJones

    (@olliejones)

    It looks to me like the convert operation completed correctly despite the web server timeout. The page removes the convert choice if no further conversion is needed. If the conversion did not complete, you’d still see the option to convert.

    You can double check this with

    wp index-mysql status

    That will diagnose any problems and complain.

    I think you’re all good. Timeouts are a pain in the you-know-what. Use wpcli for big tables and enable them one by one.

    Unfortunately the ALTER TABLE ADD KEY operations have to do an entire table at once. There’s no way to do keying operations in chunks. Or we definitely would have.

    Maybe we should try using an immediate one-off wpcron task.I’m not sure I understand all the gnarly relationships between database thread, cron, and timeouts to trust that approach.

    • This reply was modified 2 years, 7 months ago by OllieJones.
    Plugin Author OllieJones

    (@olliejones)

    I just had a chance to look at your upload.

    You should do

    wp index-mysql enable wp_postmeta 
    wp index-mysql enable wp_users
    wp index-mysql enable wp_comments

    to complete your re-keying job.

    Thread Starter mikacns

    (@mikacns)

    My bad – the uploaded ID I provided was from the production website, not the staging where I actually tested it. On production I merely installed the plugin, but haven’t performed any actions with it.

    Strangely enough on staging website, the index for WooCommerce orders seems to be removed no matter what I try to do (add or revert keys). When I search orders using email or name it doesn’t return any results. Is there a way to re-create the standard keys, so I can test this out more?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Re-run after a timeout?’ is closed to new replies.