Memcached creates 504 Gateway Timeout

  • Resolved michael3502

    (@michael3502)


    5 years, 6 months ago

    Recently, our site started to get “504 Gateway Timeout” error messages on the back-end when logging in and sometimes on the front-end. When “memcached” was disabled in the SG Optimizer plugin, the problem went away.

    Apparently, memcache was using too much memory for normal processing of other processes to complete in the 120 second default server timeout delay. Why memcache should create this problem is unclear as a feature that is supposed to speed up delivery is in fact slowing it down. Perhaps there is an incompatibility with another plugin but I do not know how to debug this problem properly. In any case memcache seems incompatible with our site at present. Any ideas?

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

Viewing 1 replies (of 1 total)
  • Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    Hey @michael3502

    The issue you have is due to 1 MB Object Size Limit. If you have an option set to autoload which has very big value (let’s say a lot of text), the memcache will get the following error:

    `ERVER_ERROR object too large for cache

    We will check this issue and will try to fix it in the upcoming versions by somehow configure the dropin to not send big keys to Memcached at all.

    Unfortunately, there is not a solution for this issue yet, so I recommend you to disable he memcache, until we fix the issue.

    Regards,
    Stanimir

Viewing 1 replies (of 1 total)
  • The topic ‘Memcached creates 504 Gateway Timeout’ is closed to new replies.