Breaks website if Redis server goes down

  • Resolved Brian Mutende

    (@picocodes)


    2 months, 2 weeks ago

    This plugin throws an error if the Redis server is not recheable which is an issue if you don’t have uptime monitoring set up.

    Instead of throwing an error, why not email the site admin and then disable object cache? That way the site admin can log in and manually re-enable object cache. (If you’re worried about stale data, you can flush the cache whenever someone enables object cache).

    This is a better solution than waking up to lost sales or dozens of support tickets simply because my redis server was corrupted.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    Because Redis is required, just like when SQL goes down your site stops responding.

    If you’d like to add your feature suggestion about sending emails about Redis not being available, you can open a pull request of GitHub.

    Thread Starter Brian Mutende

    (@picocodes)

    I’m not hating. I’m also a plugin dev. It’s just that this plugin cost me $500+ in sales because my Redis server failed. Had to switch to Litespeed cache which doesn’t break the site when Redis is down.

    Unlike SQL, Redis is not required to run WordPress. Auto-deactivating the object cache when Redis is down is better than breaking the site. But hey, it’s your plugin so do with it as you wish.

    Plugin Author Till Krüss

    (@tillkruess)

    Had to switch to Litespeed cache which doesn’t break the site when Redis is down.

    Your cache will go stale while Redis is down, and it’s back up WordPress will sync the stale data back to SQL and you will have corrupted data — at some point.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.