Redis does not reconnect as expected.

[abulvenz]

Describe the bug
Reflex does not reconnect to redis when connection was lost.

To Reproduce
Steps to reproduce the behavior:

• Start app using redis
• Stop redis
• Immediately restart redis
• When doing some state changes you only see redis.exceptions.ConnectionError: Connection closed by server.
• The frontend is dead by now.
• Restart app, everything works again.

Expected behavior
Reflex should automatically try to reconnect on connection errors and log a warning.

Are there any configuration options that I missed?

[ElijahAhianyo]

seems like the connection is created when the StateManager is created which is done once. We probably need a polling mechanism that times out after x period before connectionError is thrown

[abulvenz]

@ElijahAhianyo Thanks for responding so fast!
Maybe we can also try to solve this via configuration?
The Redis-constructor seems to accept some retry-arguments.

[abulvenz]

@ElijahAhianyo I'm sorry, just checked, that retrying is already the default for the client, but not for individual calls on the client.

So we would need to have something in redis that catches the errors and either retries the state change/loading or skips it.
Implementation idea of @benedikt-bartscher: Create a @redis_retry-decorator that wraps the relevant functions.

At least the backend should not be blocked permanently by those errors. What do you think?

[benedikt-bartscher]

Related: #3506