Change to database locking is still flooding our databases

  • webbuilder.leap

    (@webbuilderleap)


    6 years, 7 months ago

    Updating from 6.3 to 6.4 crashed our multisite networks because our database servers couldn’t handle the load caused by the switch to database locking instead of file locking. Updating to 6.5.1 didn’t help, even though the bug is said to be fixed in that version. Does anyone know if there’s a way to turn off database locking?

Viewing 1 replies (of 1 total)
  • pronl

    (@pronl)

    6 years, 7 months ago

    @webbuilderleap

    Despite the bug fix in 6.5.1 there is still a fundamental issue with database locking using the WP_SITEMETA table in a MultiSite env.

    It is possible to resolve this fundamental problem, though it does require a core table edit in the database. A unique index needs to be added to the WP_SITEMETA table.

    (There is an old entry in the WordPress MU tracking system which requested for adding the UNIQUE index to the WP_SITEMETA table in core. But for some reason it was reverted and never made it into core …).

    Manually adding the UNIQUE index can only be done properly after making sure no duplicate site_id,meta_key records exist. In other words, you really need to know what you are doing.

    All of this is based on the short input provided so far in this topic.
    So I could be wrong 😉

    Oh, and no there doesn’t seem to be a way to disable database locking in the plugin.

Viewing 1 replies (of 1 total)
  • The topic ‘Change to database locking is still flooding our databases’ is closed to new replies.