-
Notifications
You must be signed in to change notification settings - Fork 23.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redis cluster,config set notify-keyspace-events Ex, but can't Trigger redis expired event #5310
Comments
@hongliuliao |
@huirss -
Reading through the original, are you saying that expiry events are not
broadcasted in the cluster? Are you successful in listening to *other*
keyspace notification in the cluster?
|
Note: keyspace notifications are node-specific, unlike regular pub/sub which is broadcast from all nodes. So: you (or the library you are using) would need to attach to all nodes to reliably get keyspace notifications from cluster. |
Thanks @mgravell, GTK (or be reminded ;)). This issue can be closed, as it is a question that was answered. |
@mgravell Hi Marc, Can you help me with adding nodes for subscriptions? I mean do I need to provide HOST IP or NodeID of each node? |
@dealslama as keyspace notifications are not broadcasted in the cluster you'll have to:
|
Need to modify the configuration on each node |
This has been also added to the documentation via redis/redis-doc#1367 Closing - feel free to reopen or create a new issue if needed. |
Hi,I use redis cluster,config set notify-keyspace-events Ex, but it couldn't Trigger redis expired event,
like this:
container.addMessageListener( messageListener(), new ChannelTopic( "keyevent@0:expired" );
but standalone it's success;
What should I do?
Thanks;
The text was updated successfully, but these errors were encountered: