• Resolved blindstuff

    (@blindstuff)


    Hi,

    We’ve been using this plug-in succesfully with a self-hosted version of Redis for some time. Thanks for the great solution.

    Our site has grown to the point where we would prefer to use a dedicated service for object cache. We’re using ElastiCache with Valkey (and have also tested Redis), however we’re encountering a configuration issue in both the Serverless and Cluster approaches.

    Config:
    define( ‘WP_REDIS_HOST’, ‘xxx.cache.amazonaws.com’ );
    define( ‘WP_REDIS_SCHEME’, ‘tls’ );
    define( ‘WP_REDIS_PREFIX’, ‘abc-123-prefix’ );
    define( ‘WP_REDIS_DATABASE’, 0);

    Error:
    Error establishing a Redis connection
    CROSSSLOT Keys in request don’t hash to the same slot

    Any insights to guide on the issue resolution? Thank you!

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

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

    (@tillkruess)

    I strongly advise against using the “cluster mode”, but if you want to use a cluster you need to check the README on how to connect to it. WP_REDIS_HOST won’t work.

    Thread Starter blindstuff

    (@blindstuff)

    Hi @tillkruess,

    Appreciate the quick response.

    In the case of ElastiCache serverless a single endpoint is provided.

    Without additional information its not exactly clear how to use the define( ‘WP_REDIS_CLUSTER’) option which is what I assume this is what you were referring to.

    Running a new ElastiCache setup without cluster mode did work as you had indicated.

    Thank you

    Plugin Author Till Krüss

    (@tillkruess)

    If you get a single cluster entry point, you can give that to WP_REDIS_CLUSTER.

    Thread Starter blindstuff

    (@blindstuff)

    Thank you, Till.
    We have opted to use non-cluster server over serverless for now.
    Can consider this resolved. Appreciate the help!

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