-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autoreconnection #25
Comments
as workaround i using this: https://github.com/kostya/redisoid |
That's good feedback. I'll look into it. |
@stefanwille - just a quick question - will And of course huge thanks for this shard <3 |
i think i will create pull request, but current code need some refactor |
* Fixed stefanwille#55, catch all possible socket/connection errors and raise Redis::ConnectionError. * Fixed stefanwille#25, when client execute command and get Redis::ConnectionError, it reconnect to redis server and reexecute last command. * Error connection to redis server now raises Redis::CannotConnectError. * Redis::DisconnectedError replaced with Redis::ConnectionError.
* Fixed stefanwille#55, catch all possible socket/connection errors and raise Redis::ConnectionError. * Fixed stefanwille#25, when client execute command and get Redis::ConnectionError, it reconnect to redis server and reexecute last command. * Error connection to redis server now raises Redis::CannotConnectError. * Redis::DisconnectedError replaced with Redis::ConnectionError.
would be nice if client have auto reconnection mode, because most production redis-servers have option
timeout 300
, and slow clients often failed with RedisError: Disconnected. And redis-rb have no this problem.The text was updated successfully, but these errors were encountered: