Jetpack sync creating thousands of orphan options

  • Resolved smithy468

    (@smithy468)


    6 years, 8 months ago

    Hi,

    After using Advanced DB Cleaner to remove orphan options from my database, I realized that Jetpack is creating many thousands of orphan options in my database and bloating the table to almost 1 GB.

    I can delete them with the plugin, but when I come back a few hours later, there are already 990 new orphan options from the same option.

    The name of the option starts with “jpsq_full_sync” followed by a long number.

    How can I prevent all of these orphan options from bloating my database?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support lizkarkoski

    (@lizkarkoski)

    Good morning @smithy468 –

    I’ve taken a look at your site through our diagnostic tool and can see that we just ran a full sync – and it is very possible that you were having a look while this was going on.

    In any case, there’s certainly a discrepancy noted in the debug:

    Queued up: 42844 items
    Sent: 39582 items

    I am going to file a report about this with our development team so they can take a closer look at what is going on.

    In the meantime, feel free to use the schedule full sync button under Sync in the debug report. Run your site at https://jetpack.com/debug/ to get started.

    Write back to me here with any other questions about this. Once I file that report I’ll come back and drop a link here as well so you can follow along if you like.

    Plugin Support lizkarkoski

    (@lizkarkoski)

    Here it is:

    https://github.com/Automattic/jetpack/issues/9791

    Thread Starter smithy468

    (@smithy468)

    I ran the debug tool and it said that “everything looks great”. However, I’m still concerned about the orphaned options that Jetpack is creating. Is this going to be a regular issue? These orphaned options really add to the size of my database and I don’t really want to go in and delete orphaned options on a regular basis.

    That said, the addition of new orphaned options by Jetpack seems to have stopped (though possibly temporarily?), so I’m assuming it was because I was deleting them during a Jetpack scheduled full sync. How often does Jetpack run a full sync?

    I’m not sure what are the implications of the debug report you ran:
    “In any case, there’s certainly a discrepancy noted in the debug:
    Queued up: 42844 items
    Sent: 39582 items”

    What could that mean?

    Thanks for your help, but I’m still not really sure how I should go about optimizing Jetpack to minimize my server load and increase my site speed. I can delete scheduled chron tasks, so if needed I will delete the “jetpack_sync_cron” and “jetpack_sync_full_cron” tasks, which are scheduled every 5 minutes (seems excessive to me). What would be the consequence of doing so?

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    I’ve asked the above to one of our very own developers in here:
    https://github.com/Automattic/jetpack/issues/9791#issuecomment-398647597

    That’s the best person to whom ask your questions ??
    Feel free to follow along the thread above, and to add anything else you may think it’s useful!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    @smithy468 just a follow up as our very own Igor has left a very thorough reply to your questions: https://github.com/Automattic/jetpack/issues/9791#issuecomment-398721010

    Please feel free to chime in if you want ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Jetpack sync creating thousands of orphan options’ is closed to new replies.