Sakri Koskimies

This was caused by WP core. WP_Query will call update_post_caches, which will call Redis SET for specific queries, even though they come from cache.

Thank you for the replies. This Redis instance is running with persistence disabled.

This is after flushing cache and running for 3 minutes:

$ redis-cli info | pastebin
> https://termbin.com/4r3tc

Maxmemory and maxmemory-policy configs:

$ redis-cli CONFIG GET maxmemory
> 1) "maxmemory"
> 2) "0"

$ redis-cli CONFIG GET maxmemory-policy
> 1) "maxmemory-policy"
> 2) "noeviction"

• This reply was modified 11 months, 3 weeks ago by Sakri Koskimies.

This will not cause payment issues. No errors or other data mishandling occurs. @jethrohazelhurst

Thanks! I submitted ticket #57405.