Till Krüss

This was fixed in https://github.com/rhubarbgroup/redis-cache/commit/e3b8fb2dd44d10132da73f52e7fce30af6e2db81

I haven’t released a new version yet, but will in the next couple of weeks.

No, the location is fixed and determined by WordPress.

You must build the container with the drop-in, you can use wp redis enable to do so.

Sorry to hear that.

Can you post your invoice number and I’ll get the refund sorted out for you?

The errors socket error on read socket and read error on connection are timeouts (or high latency responses).

Can you post the output of redis-cli SLOWLOG GET?

I can’t read that, but if it’s 512MB per PHP worker and you’re seeing PHP go out of memory, try bumping it to 1024 or 2048 to see if that resolves it.

Consider using WP_REDIS_DATABASE instead ??

@daanvandenbergh Duplicate attributes shouldn’t get removed, but I can send you a license key. What’s your email?

Correct, WP_REDIS_SELECTIVE_FLUSH is unsupported and off by default, I just wanted to make sure you have it set to false.

As for Redis Server monitoring, there are various tools out there like New Relic and Datadog, if you’re already monitoring your infrastructure with a tool, they might have Redis monitoring as well.

Thanks for the sharing the logs, it’s not enough to go on, since the issue is Redis not responding at all or in time.

Object Cache Pro Consideration: We are open to exploring Object Cache Pro if it can provide enhanced stability and performance for our setup.

That’s exactly what is does, in that order ??

I see, Apache is going OOM. How much memory do you allocate for each individual PHP worker?

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.

Stoked to hear that. Feel free to copy that into a 5-star review ??

I’ve seen this issue reported 1-2 times a year, for almost a decade now and I’ve never been able to reproduce it or figure out what could cause it.

Unfortunately the only suggestion I have is to flush Redis when this loop occurs.

Hey Christopher, this happens to some sites. I see you have Query Monitor installed. Can you post the statistics it shows about the object cache usage?

Your site might be using too many keys, or Redis Server is just responding too slowly.

Can you upgrade to Object Cache Pro v1.21.2, that might resolve this issue.

Haha, funny post.

I guess you could keep an eye on Redis using the Query Monitor plugin occasionally, or just making sure your Redis statistics look good.

Ideally set up supervisord to ensure Redis Server is ALWAYS running.