Issue with AWS Elasticache

[tuctboh]

Hi,

Using this against AWS Redis (Engine 7.1.0, Clustering enabled, Multi-AZ enabled, 1 shard, 3 nodes.

I've configured it as -

define( 'WP_REDIS_HOST', 'redis-wpcache.OTHERNODESHERE.cache.amazonaws.com' );
define( 'WP_REDIS_PORT', 6379 );
// change the prefix and database for each site to avoid cache data collisions
define( 'WP_REDIS_PREFIX', 'SITENAME' );
define( 'WP_REDIS_DATABASE', 0 ); // 0-15
// reasonable connection and read+write timeouts
define( 'WP_REDIS_TIMEOUT', 1 );
define( 'WP_REDIS_READ_TIMEOUT', 1 );

for the first site. When I went to the second site, I did the same thing but just changed WP_REDIS_PREFIX and NOT the WP_REDIS_DATABASE. Everything worked fine, I wanted the Elasticache to do its work, and Redis Cache just thinks its a single instance.

Everything was running great for 4 sites until I had to do a security patch. Once I did, all 4 sites went down. It seems that it'd getting back a "MOVED" from the server and doesn't know what to do.

Is there somewhere I went wrong? Is there a setting I missed?

Tnx, Tuc

[tillkruss]

Read the docs: https://github.com/rhubarbgroup/redis-cache?tab=readme-ov-file#scaling

I'd disable "cluster mode" and use use dedicated databased for each site. Prefix flushing is slow.