Conversation
supportHi, JetPack backup has been failing with HTTP 5XX Server Error 1 files affectedMore wp_post_views JetPack support thinks it is coming from Post Views Counter. Any feedback would be appreciated. The page I need help with: [ log in to see the link]
Hi, This table is coming from Post Views Counter. But why it results in an issue? Why Jetpack tries to copy a PVC table? We’d recommend asking JetPack devs about it.
Hi, thank you for your response. This table is causing 1) the site to stop loading with a critical error, and 2) JetPack backup to fail. If I remove number_format( pvc_get_post_views( get_the_ID() ) ); from all the places I used, the site loads. If I ask the host to repair this table, it seems the loading issue gets fixed (but the problem returns in a day or two). According to JetPack support, wp_post_views has around 3.5 million rows, which suggests something is wrong. Any feedback would be appreciated. This reply was modified 9 months, 1 week ago by madflute .
Hi, You can try to do the daily views data cleanup to limit number of records in the database by setting the Cleanup Interval option to 1 day. But 3.5 million rows is not much really – these are really tiny records. We’ve seen databases with millions of heavy post records operating without any issues and dozens of millions of wp_post_views records working smoothly, generating reports etc. The issue with backing up a table would happen if the backup mechanism tries to do this in one shot – it might require too many resources to be able to process it.
Hi, This table is coming from Post Views Counter. But why it results in an issue? Why Jetpack tries to copy a PVC table? We’d recommend asking JetPack devs about it.
Hi, thank you for your response. This table is causing 1) the site to stop loading with a critical error, and 2) JetPack backup to fail. If I remove number_format( pvc_get_post_views( get_the_ID() ) ); from all the places I used, the site loads. If I ask the host to repair this table, it seems the loading issue gets fixed (but the problem returns in a day or two). According to JetPack support, wp_post_views has around 3.5 million rows, which suggests something is wrong. Any feedback would be appreciated. This reply was modified 9 months, 1 week ago by madflute .
Hi, You can try to do the daily views data cleanup to limit number of records in the database by setting the Cleanup Interval option to 1 day. But 3.5 million rows is not much really – these are really tiny records. We’ve seen databases with millions of heavy post records operating without any issues and dozens of millions of wp_post_views records working smoothly, generating reports etc. The issue with backing up a table would happen if the backup mechanism tries to do this in one shot – it might require too many resources to be able to process it.