Redis setEX Expired Event Triggering Multiple Times Despite Unsubscribe/Resubscribe about redis HOT 9 OPEN

@Prem-Kumar-98 can you share your test code?
from my testing it's generally not a redis issue, maybe relate to client.

from redis.

Hi @sundb ,
Below is the code snippet for the test method as requested. I've replaced sensitive information with generic placeholders for confidentiality:

Class exampleFileName(){

Constructor() {
    this.client = RedisInstance.getRedis();
    this.redisService = RedisSubscriberClient.getRedis();
}

async testMethod() {
  await this.client.unsubscribe("__keyspace@0__:" + timerKey);
  await this.redisService.setex("__keyspace@0__:" + timerKey, 60);
  this.client.subscribe("__keyspace@0__:" + timerKey, (message, channel) => {
    console.log("Testing event triggered", message, channel);
  }).then((response) => {
    log.info("Timer set! " + response);
  });
}
}

Let me know if you need further assistance or clarification.
I have a question regarding the behavior of a node-redis client. If a node-redis client subscribes to a channel twice with different instances, will it emit the expired event twice?

from redis.

I have a question regarding the behavior of a node-redis client. If a node-redis client subscribes to a channel twice with different instances, will it emit the expired event twice?

yes, they are two connections.

from redis.

So, as you can see, i'm unsubscribing the channel before subscribing to it. In this case, why is the expired event emitting twice in the rarest case?

from redis.

@Prem-Kumar-98 can you share the notificatiions you received?

from redis.

Hi @sundb , I don’t have logs or notification details. I'm using GCP Redis Labs, and I could see the subscribed callback got triggered twice.

  this.client.subscribe("__keyspace@0__:" + timerKey, (message, channel) => {
    console.log("Testing event triggered", message, channel);
  })

from redis.

@Prem-Kumar-98 what's your config notify-keyspace-events?
first at all, if you are using KEA, the script you give will receive three notification:

__keyspace@0__k set
__keyspace@0__k expire
__keyspace@0__k expired

from redis.

@sundb ,Keyspace event I configured the cloud service and verified that with the configuration I have from my end, it will emit the event only for expired, because it's not happening all the time; in the rarest case, it's emitting the expired events twice.

from redis.

@Prem-Kumar-98 sorry, from the clues i don't know the reason.
go through the code, the expired notification was just send from one place, at the same we will remove it from the database.
i don't think one key can be expred two times.

from redis.