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
In our project we use password-protected Redis instance for writing.
Right after RedisClient creation it is more or less trivial to AUTH to it (and SELECT if it is needed), but if connection was lost afterwards, Rediscala do not provide any useful info about reconnection and also do not store AUTH data in connector actor to authentificate itself automatically.
Thus if we want to re-authenticate ourselves we need to either check Future's failures for "ERR Operation not permitted" messages or parse logs.
I think it would be very useful to provide some form of callback or listener to connection state changes. Also, it could be useful (but not too secure) to store last used AUTH and SELECT data to auto exec them right after reconnection.
The text was updated successfully, but these errors were encountered:
In our project we use password-protected Redis instance for writing.
Right after
RedisClient
creation it is more or less trivial toAUTH
to it (andSELECT
if it is needed), but if connection was lost afterwards, Rediscala do not provide any useful info about reconnection and also do not storeAUTH
data in connector actor to authentificate itself automatically.Thus if we want to re-authenticate ourselves we need to either check Future's failures for
"ERR Operation not permitted"
messages or parse logs.I think it would be very useful to provide some form of callback or listener to connection state changes. Also, it could be useful (but not too secure) to store last used
AUTH
andSELECT
data to auto exec them right after reconnection.The text was updated successfully, but these errors were encountered: