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
If Redis is down (e.g. temporarily), my application fails to start. It'd be more consistent that client construction was separate from actually trying to talk to Redis. If Redis is available, then application starts fine, then Redis becomes unavailable and Redis I/O just fails - application still works otherwise. Would be more consistent if startup of my application was not affected by Redis availability.
Would it be possible to change the behavior like this? Try to connect to Redis asynchronously or on first use?
The text was updated successfully, but these errors were encountered:
If Redis is down (e.g. temporarily), my application fails to start. It'd be more consistent that client construction was separate from actually trying to talk to Redis. If Redis is available, then application starts fine, then Redis becomes unavailable and Redis I/O just fails - application still works otherwise. Would be more consistent if startup of my application was not affected by Redis availability.
Would it be possible to change the behavior like this? Try to connect to Redis asynchronously or on first use?
The text was updated successfully, but these errors were encountered: