luin/ioredis

A delightful, performance-focused Redis client for Node and io.js.

Christian Roy

@roychri

You cannot use "subscribe" on the same connection that you use other commands.

Make a new connection for your subscribe.

redisSubscribe = new Redis();

or whatever

Jason Shin

@JasonShin

ahh right

Jason Shin

@JasonShin

hey @roychri I still do not receive any subscribe event for the key expire

what's wrong with above code?

Creating a new instance as redisSubscriber resolved the connection issue

however, there's no expire events received in the subscribe block

Christian Roy

@roychri

Are you using docker run or docker-compose or something else?

Jason Shin

@JasonShin

I'm using docker compose

Christian Roy

@roychri

docker-compose exec redis-master redis-cli config get notify-keyspace-events

Replace redis-master with the name of the redis service in your compose file. What do you get?

Jason Shin

@JasonShin

1) "notify-keyspace-events"
2) ""

ahh...

T_T !!

im dumb

Christian Roy

@roychri

Did you change the command in your docker-compose.yaml ?

Jason Shin

@JasonShin

nope

Christian Roy

@roychri

You have to tell redis to use your new config file

Jason Shin

@JasonShin

yeah right

1) "notify-keyspace-events"
2) "xE"

ok cool

Christian Roy

@roychri

I do not think xE will send the __keyevent@0__:expire event but rather the __keyevent@0__:test event (with the name of your key in the event name).
If you want __keyevent@0__:expire then you should set it to xK I think.

Jason Shin

@JasonShin

I see

Christian Roy

@roychri

But Maybe your right and im mixing them up, tias

Jason Shin

@JasonShin

still, no events

1) "notify-keyspace-events"
2) "xK"

Christian Roy

@roychri

and no events with xE either?

Jason Shin

@JasonShin

nope

I only get a very first

zz null 1 undefined undefined undefined

which means nothing

it's from

redis2.subscribe('__keyevent@0__:expired', (x, y, c, v, b) => {
    console.log('zz', x, y, c, v, b);
  });

^^ testing code

Christian Roy

@roychri

Enable all events (AKE instead of xK) and in another terminal use redis-cli monitor to see the events being sent after you docker-compose restart app...

Jason Shin

@JasonShin

1550539085.729667 [0 192.168.0.3:56496] "info"
1550539085.750826 [0 192.168.0.3:56498] "info"
1550539085.751758 [0 192.168.0.3:56498] "set" "test" "12" "EX" "1"
1550539085.751925 [0 192.168.0.3:56498] "set" "test" "12" "EX" "2"
1550539085.752053 [0 192.168.0.3:56498] "subscribe" "__keyevent@0__:expired"

after that, nothing fires inside the subscribe code

Christian Roy

@roychri

Using redis 2.8.0 or later?

Jason Shin

@JasonShin

yeah

I'm using 5.0.0

Christian Roy

@roychri

I recommend you read this again and see if you missed anything...
https://redis.io/topics/notifications

Jason Shin

@JasonShin

ok I will do that

@roychri a quick question, how do you listen to all these events using cli?

I just want to test this without ioredis

Christian Roy

@roychri

redis-cli monitor will show them I think

Jason Shin

@JasonShin

so when the key expires, what will be logged in redis-cli monitor?

Christian Roy

@roychri

If the notifications are enabled, yes, I think so

Jason Shin

@JasonShin

I've bascially enabled everything notify-keyspace-events AKExes

but still nothing shows up on neither redis-cli monitor and .subscribe('__keyspace@0__:expire', and .subscribe('__keyevent@0__:expire',

Christian Roy

@roychri

AKE would have been enough, since A means all

Where communities thrive

People

Repo info

Activity