You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
We are using Redis-sentinel with KUE for redis failover. Once the failover is done. it seems the connections are getting reconnected to new master, however the channels on which if there is a worker subscribe to (or if there is previously a publisher holding a connection) unable to receive anything.
Is it a problem with sentinel or with the redis client itself. Similarly, the publisher is unable to publish to the channel with the new master (after reconnecting to new master).
We found out a way, that is a kind of HACK , but looking if there is a proper solution to the problem. As even KUE said it properly supports redis-sentinel library by creating connectionFactory.
The text was updated successfully, but these errors were encountered:
Hi,
We are using Redis-sentinel with KUE for redis failover. Once the failover is done. it seems the connections are getting reconnected to new master, however the channels on which if there is a worker subscribe to (or if there is previously a publisher holding a connection) unable to receive anything.
Is it a problem with sentinel or with the redis client itself. Similarly, the publisher is unable to publish to the channel with the new master (after reconnecting to new master).
We found out a way, that is a kind of HACK , but looking if there is a proper solution to the problem. As even KUE said it properly supports redis-sentinel library by creating connectionFactory.
The text was updated successfully, but these errors were encountered: