Cannot connect to AWS Redis in cluster mode. (Using ioredis it works)

[jisaacks]

Description

Here is my code:

import { createCluster } from "redis";

export async function makeClient() {
  const client = createCluster({ rootNodes: [ { url: process.env.REDIS_URL } ] })
  .on('error', err => {
    console.log('Redis Client Error', { err })
  }).connect()

  return client
}

This will not error but it hangs forever.

The REDIS_URL is formatted like: rediss://:XXXXXX@HOST:PORT?ssl_cert_reqs=optional

However it works if I use ioredis with this code:

import Redis from 'ioredis'

const [_, password, host, port] = process.env.REDIS_URL!.match(/rediss:\/\/:(.*)@(.*):(\d*).*/)!

const Cluster = new Redis.Cluster([
  {
    host,
    port: Number(port),
  }
], {
  dnsLookup: (address, callback) => callback(null, address),
  redisOptions: {
    password,
    tls: {}
  }
})

console.log({ Cluster })

Being that ioredis is depricated I would prefer to use this library. Is there a solution?

Node.js Version

v18.20.8

Redis Server Version

No response

Node Redis Version

No response

Platform

No response

Logs

[nkaradzhov]

@jisaacks thank you for raising this, we will take a look

[captmiddy]

Seeing the exact same issue with VALKEY clusters in Amazon Elastic Cache. It works fine with serverless but as soon as I put up a cluster it fails to connect and just hangs. If I attempt to connect I get MOVED errors because it isn't in cluster mode. Even putting all 9 of the nodes into the set, it will not connect. Due to heavy usage I would prefer not to be in serverless mode long term as the costs will be high.

I adjusted the client above to include password and username as I have authentication and SSL turned on. If I do createClient rather than createCluster it works to connect but can not handle getting redirected.

[dchanm]

We ran into a similar issue with ElastiCache + TLS. We had to enable TLS via defaults

const client = createCluster({
  rootNodes: [ { url: ... } ],
  defaults: {
    socket: { tls: true }
  }
})

The initial configuration connection occurs TLS since we use rediss://. The following node connections failed since they were over plaintext and our cluster forces TLS (in-transit encryption enabled). Setting the socket option fixed the issue.

This was on 5.9.0