WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #35096, comment 4


Ignore:
Timestamp:
12/15/2015 12:25:09 PM (4 years ago)
Author:
SergeyBiryukov
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35096, comment 4

    initial v1  
    1 The conditions are not obvious. As noted in the other ticket they are also hard to script because of the `WP_INSTALLING` flag. I believe it has to do with the size of options object growing beyond the limits of Object-Cache backends. When the set fails, there's no fallback to a memory cache. The default object size of e.g. memcached is 1M and its very common for plugins to accidentally add autoloading options (https://core.trac.wordpress.org/ticket/18244) so you could see the options table growing beyond this size in many situations on the large multisite installs affected by this bug.
     1The conditions are not obvious. As noted in the other ticket they are also hard to script because of the `WP_INSTALLING` flag. I believe it has to do with the size of options object growing beyond the limits of Object-Cache backends. When the set fails, there's no fallback to a memory cache. The default object size of e.g. memcached is 1M and its very common for plugins to accidentally add autoloading options (#18244) so you could see the options table growing beyond this size in many situations on the large multisite installs affected by this bug.