-
Notifications
You must be signed in to change notification settings - Fork 21
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
Reconnect behaviour differs from cpan Redis module #73
Comments
I think that because the |
i've tried with 100_000. same:
|
shogo82148
added a commit
that referenced
this issue
Jan 27, 2018
shogo82148
added a commit
that referenced
this issue
Jan 28, 2018
Changelog diff is: diff --git a/Changes b/Changes index 65e5608..acf2fb3 100644 --- a/Changes +++ b/Changes @@ -2,6 +2,9 @@ Revision history for Redis {{$NEXT}} +0.21 2018-01-28T01:02:14Z + - Fix reconnect behaviour differs from cpan Redis module #73 + 0.20 2017-02-25T22:48:26Z - Fix build issue on newer Perl
I fixed this issue, and released Redis::Fast v0.21. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
so, script:
will print the following:
if I stop redis server (after that first
err: Could not connect to Redis server
line emited), and then start it in a few minutes (after all reconnect attemts exhaused)$redis
connect does not work even with live Redis server, it still emits "err: Not connected to any server".In contrast behaviour with
Redis
module:i.e. the handle still can be used after redis server up.
Not sure which behaviour is more correct, but the fact is they differs.
Also our use case when we prefer
Redis
module behaviour:we have long running daemons and if redis server down for several minutes we have to restart all daemons and cannot use reconnect feature, or we have to write special code in every
eval
after which we would want to connect again.The text was updated successfully, but these errors were encountered: