Unable to access the RedisClient using RedisSentinel in order to call the get or set methods [SimpleError: ERR unknown command 'GET', with args beginning with: 'key']

[pulpiks]

Description

const addresses: LookupAddress[] = await new Promise((resolve, reject) => { dns.lookup( "wso2-authentication-service-redis-service", dnsOptions, (err, addresses) => { if (err) { console.error("DNS resolution error:", err); reject(err); } else { console.log("Resolved addresses:", addresses); resolve(addresses as LookupAddress[]); } }, ); });

console.log("addresses", addresses);  

Resolved addresses: [
{ address: '100.64.128.230', family: 4 },
{ address: '100.64.42.138', family: 4 },
{ address: '100.64.62.26', family: 4 }
]

const sentinelClient = await createSentinel({
  name: "wso2-authentication-service",
  sentinelRootNodes: addresses.map((address) => ({
    host: address.address,
    port: 6379,
  })),
})
  .on("reconnecting", () => {
    console.log("Redis sentinel reconnecting");
  })
  .on("error", (err) => {
    console.error(`Client Redis sentinel  connection error: ${err}`);
    throw new Error(`Client Redis sentinel  connection error: ${err}`);
  })
  .on("ready", () => {
    console.log("Redis sentinel connection is ready");
  })
  .connect();

console.log(sentinelClient.isReady); **// true**
console.log(sentinelClient.isOpen); **// true**

const res = await sentinelClient.use(async (client) => {
  try {
    const value = await client.get("dfsf");
    console.log("value", value);
    return value;
  } catch (error) {
    console.error("Error in sentinelClient.use", error); 
    **Error in sentinelClient.use[SimpleError: ERR unknown command 'GET', with args beginning with: 'key' 'dfsf' ]**
  }
});`

Please help me fix this issue.
PS. I tried to find workarounds like using .acquire, .getMasterNode, and .createClient right after, but it complains about calling basic Redis client methods such as .get and .set.

Node.js Version

v22.14.0

Redis Server Version

Redis server v=7.2.7 sha=00000000:0 malloc=libc bits=64 build=7f24f11dd7e42c58

Node Redis Version

^5.0.1

Platform

No response

Logs

[htemelski]

Hello @pulpiks,
I'm unable to replicate your issue. Could you please help me better understand your setup and its topology?

[pulpiks]

Yes, sure. I reproduce it locally as shown below.

Assume, I have 3 sentinel nodes(127.0.0.1:26379, 127.0.0.1:26380, 127.0.0.1:26381) running via docker.

each of sentinel1(2)(3).conf looks like:

port 26379(26380)(26381)
daemonize no
pidfile "/var/run/redis-sentinel.pid"
logfile ""
dir "/tmp"
sentinel deny-scripts-reconfig yes
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 180000
sentinel config-epoch mymaster 3

I'm also running redis-server on port 6379.

So, then I try to do:

const sentinel1 = await createSentinel({
name: "mymaster",
sentinelRootNodes: [
{
host: "127.0.0.1",
port: 26379,
},
{
host: "127.0.0.1",
port: 26380,
},
{
host: "127.0.0.1",
port: 26381,
},
],
})
.on("reconnecting", () => {
console.log("Redis sentinel reconnecting");
})
.on("error", (err) => {
console.error(Client Redis sentinel connection error: ${err});
throw new Error(Client Redis sentinel connection error: ${err});
})
.on("ready", () => {
console.log("Redis sentinel connection is ready");
})
.connect();

so it's failing here

throw new Error(Client Redis sentinel connection error: ${err});

Error: Client Redis sentinel connection error: obseve client error: Error: read ECONNRESET

Remotely I have a bit different set up. The difference is I dont have running redis-server remotely, only 3 sentinels on diffrent hosts on kube cluster but on the same port 6379.

There I can connect to createSentinels as shown in my first message but all methods as .get, .set are failing

[htemelski]

Seeing different errors makes me think that there's an issue with the Docker setup and its networking.

Could you try running the following script and sharing the output?

index.js

let tracer = [];
try {
  const sentinelClient = await createSentinel({
    name: masterName, 
    sentinelRootNodes: [{
      host: sentinelHost1, 
      port: sentinelPort
    },{
      host: sentinelHost2, 
      port: sentinelPort
    },{
      host: sentinelHost3, 
      port: sentinelPort
  }]
  }).on("reconnecting", () => {
    console.log("Redis sentinel reconnecting");
  }).on("error", (err) => {
    console.error(`Client Redis sentinel  connection error: ${err}`);
    throw new Error(`Client Redis sentinel  connection error: ${err}`);
  }).on("ready", () => {
    console.log("Redis sentinel connection is ready");
  });

  sentinelClient.setTracer(tracer)

  await sentinelClient.connect()

  await sentinelClient.use(async (client) => {
    const value = await client.get("dfsf");
    console.log("value", value);
  });
} catch (error) {
  console.error(error);
  console.log("tracer:", tracer)
}

[pulpiks]

Client Redis sentinel connection error: obseve client error: Error: Socket closed unexpectedly
~/Projects/wso2-authentication-service/src/common/infrastructure/redis/redis.utils.ts:144
throw new Error(Client Redis sentinel connection error: ${err});
^

Error: Client Redis sentinel connection error: obseve client error: Error: Socket closed unexpectedly
at Class. (/Users/GY35MF/Projects/wso2-authentication-service/src/common/infrastructure/redis/redis.utils.ts:144:17)
at Class.emit (node:events:518:28)
at RedisSentinelInternal. (/Users/GY35MF/Projects/wso2-authentication-service/node_modules/@redis/client/lib/sentinel/index.ts:316:44)
at RedisSentinelInternal.emit (node:events:518:28)
at Class. (/Users/GY35MF/Projects/wso2-authentication-service/node_modules/@redis/client/lib/sentinel/index.ts:1026:42)
at Class.emit (node:events:518:28)
at RedisSocket. (/Users/GY35MF/Projects/wso2-authentication-service/node_modules/@redis/client/lib/client/index.ts:567:14)
at RedisSocket.emit (node:events:518:28)
at RedisSocket.#onSocketError (/Users/GY35MF/Projects/wso2-authentication-service/node_modules/@redis/client/lib/client/socket.ts:264:10)
at Socket. (/Users/GY35MF/Projects/wso2-authentication-service/node_modules/@redis/client/lib/client/socket.ts:253:28)

Node.js v22.14.0

createSentinel is refusing the connection.

Also, want to check:

1. I have running redis-server on 6349, is this needed or not while using redis sentinel? If I would like to have 2 sentinels, should I have 4 running instances (1 redis server and 3 sentinels) or only 3 sentinels?
2. If I use const client = await createClient({
   url: redis://127.0.0.1:6379,
   })
   .on("error", (err) => {
   console.error(Redis connection error: ${err});
   throw new Error(Redis connection error: ${err});
   })
   .on("ready", () => {
   console.log("Redis connection is ready");
   })
   .connect();
   it connects to redis successfully in that case but I'm afraid it's not using sentinels or maybe it uses, so I need clarification on that

[htemelski]

You need an odd number of sentinels (at least 3 in order to reach quorum) and redis-server (with replicas)

[pulpiks]

yes it means everything is correct in terms of configuration and the problem is with the code or library