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
I was wondering if it's possible to change the redis backplane while using the CacheManager? Suppose that the CacheManager instance is a static readonly instance in my code. And I'm using that instance with specific redis backplane configuration (ip, port, password, dbid). What if I wanted to change the password? Or, what if I wanted to change the ip&port (I may prefer to change the redis instance for caching) or even dbid? Can I make these changes on CacheManager while not wiping out the local inmemory cache but only wiping out redis backplane?
Best regards.
The text was updated successfully, but these errors were encountered:
Hi @rebulanyum,
Great question.
CacheManager currently doesn't support any feature to re-configure the Redis connection.
Although there is already a wrapper around the Multiplexer object, I never added that as a feature.
For the backplane, that might be a little bit more tricky because of the long running "subscribe" connection.
But yeah, would be a good addition, I'll add that as a feature request.
This may be a blocker stopping my organisation using Cache Manager. Our web application is a long running application and downtime is expensive for our customers.
Hello @MichaCo .
I was wondering if it's possible to change the redis backplane while using the CacheManager? Suppose that the CacheManager instance is a static readonly instance in my code. And I'm using that instance with specific redis backplane configuration (ip, port, password, dbid). What if I wanted to change the password? Or, what if I wanted to change the ip&port (I may prefer to change the redis instance for caching) or even dbid? Can I make these changes on CacheManager while not wiping out the local inmemory cache but only wiping out redis backplane?
Best regards.
The text was updated successfully, but these errors were encountered: